-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] dynamic replace-query
#2465
Comments
I second this. I was myself looking for a similar feature which would let me work around a nr of limitations I'm finding when using E.g. in my case this would unblock me in #2456 because as a hacky workaround I would simply make sth like |
I would also like such a thing. I basically want to be able to do my own search and set the query based on the results while still keeping all the options originally provided (i.e. I don't want to reload). This would filter the original input, but still allow for other things to be selected. From what I can tell, the command isn't optional for any of the actions that take one in. So instead of overloading I'd basically use it like this: |
I've created a PR for this: #2559 I'm not exactly sure how to go about contacting a maintainer to authorize workflows for me though. |
This is not difficult to do.
You need to replace the � with U+001B locally. |
man fzf
)Info
Idea
I'd like to create a "search engine" widget similar to Alfred/Albert or the Firefox/Chrome omnibar. To make this work, I want the user to be able to type in (customizable) triggers to perform different searches/actions:
I can achieve the functionality of this already by using
change
andreload
to switch the logic based on the trigger sequence:But I can't quite achieve the look that I want, because the trigger sequence of course is still displayed in the query.
Whereas what I really want is to either
Either of those options would allow me to mimic the omnibar search engine functionality to do something like this:
I'm guessing this would look something like:
Note that we can get pretty close here with the
--header-lines
option. But presumably being able to rewrite the query at will would open up other nifty features (syntax highlighting?). There are some complications, like what to do with the cursor if you're not at the end of the line (maybe pass the cursor position as a second argument toformat_query
?)See also my feature request for multi-character trigger sequences.
The text was updated successfully, but these errors were encountered: