Suggestion: Existing text in search box should be selected

I very much like that RepoZ remembers my previous search/filtering and shows this in the text box as I often do want to access the same projects, but I think it would be much nicer if this existing text in the search box was “selected” so that it is easy to overwrite with a different search. As I see it, there are three possible “scenarios” when I activate RepoZ.

1. I am happy with the current search text and just want to interact with one of the items found.
2. I want to append something to the existing text to refine my search
3. I want to find something completely different.

Case 1 is probably the most common case for many, but after that I think case 3 is probably much more frequent than case 2.

The way it is now, I am ready for case 2, but if I want case 3 (overwrite text), I have to use something like <shift><ctrl><left-arrow>. If the text were pre-selected, I would be ready for case 3 (overwrite), and if I wanted case 2 instead (append) then it is just a single <right arrow> to remove the selection and keep typing.

Another argument for this behaviour is that it becomes much more geared towards “reflex interaction” just like e.g. app launchers like Alfred or similar. As a user I just want to be able to press the repoz hot-key and start typing a few letters “without thinking”. I don’t want to have to actively look at a tiny search box in the corner of my big screen and consciously evaluate if I need to delete existing text first or not before typing. For most developers (and other RepoZ users I guess) occasionally retyping a few letters in a search is probably much much faster than the “stop to look and think” process.

Anyway, these are my thoughts. I would love to hear what you think about it @awaescher (and others of course).

[awaescher]

By the way, this is how it works on macOS already 😁

[awaescher]

Thanks for these insights, this was actually very helpful to me. You got some really good points here. In addition, pre-selecting the text is likely to be the easiest fix to implement as well 😄