Trim history search pattern
It is very easy to copy an SHA1 including some whitespace into the
search field, as I accidentally did today. Therefore trimming seems
useful here.
Add logic to prevent starting multiple search jobs for the same
trimmed pattern. This could happen easily now when the user is
typing in a search pattern containing blanks (such as "history
search": we'd get two identical jobs for raw inputs "history"
and "history ").
Change-Id: I875530b45c5745a8fe9d6d5972bfc4f357391303
Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de>
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>