Search the Community
Showing results for tags 'query history'.
Found 2 results
I use the query history feature a lot and, in my up-arrow frenzy, I often overshoot the entry I want. To get back to it, I clear out the alfred prompt and start from the beginning, going more slowly this time. It'd be nice if there was a way to go forwards through the history, so that I could correct my overshoot more easily. My thought was that the down arrow would be a natural way to do this. I realize that the down arrow is currently used as a way to disengage query history mode, but the left and right arrow keys also do this, and it's rare that I want to disengage at all.
By "modal" query type I mean one created by connecting a hotkey directly to a script filter, or by calling an external trigger directly connected to a script filter. (Alfred then show's that script filter's icon (in place of Alfred's) and directs all input to that script filter - no keyword is being shown.) As an aside: is there an established/better name for this? - Currently, the typed-query history (pressing up-arrow or, if turned on, having the last query automatically redisplayed) doesn't work in such modal queries at all. - Similarly, query strings entered in a modal query do not get recorded even in the general history. It would be helpful to have a *query-type-specific* (scoped) typed-query history in that event. I.e., when you enter such a modal query again, only *that* query's history is presented. In addition or alternatively, query strings from modal query types could be included in the general history, prefixed by their script filter's keyword (if defined). ------ I realize that I could alternatively define a hotkey to simply open Alfred with a keyword, giving me regular queries that become part of the history, but I quite like the separate mode / scope that is entered for modal query types - and it does open the door for a scoped history. Example use case: I have a modal query for searching Evernote that I activate with a hotkey. Having access to past queries there - limited to queries of that type - would be handy.