-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add a new option or parameter to enable "--no-sort" #23
Comments
Ok, yeah, the Would you like to have a keybinding to toggle it, or would you prefer an option and set it there permanently like you mentioned? |
Thank you. If it's possible I'd suggest to keep both usages, instead of choosing one of them. The original configuration is limited to one keybinding making it hard to switch between these two kind of searching. So, I think maybe it's closed to "having a keybinding to toggle it" that you mentioned...? |
Does adding something like this set -g @fuzzback-finder-bind 'ctrl-s:toggle-sort'
# or whichever shortcut you prefer to your tmux config work? that way you can toggle it on and off. That's what I meant with a keybinding. |
Yes, something like that. |
I'd prefer using the option I showed an example of. Creating a new launcher script is a lot more work than simply toggling sorting on and off with an existing option. |
Got it. Thanks for your working~ |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, I saw the code you mentioned. No problem now. Thanks! |
Hi,
I've used this plugin for a period of time and I met a problem on the history search. In my case, I'd like to jump to the earliest keyword appeared. For example, when there are some compilation errors appeared, I'd like to jump to the earliest one. However, without
--no-sort
,fzf
would mess up the result.I've tried to modify
$FZF_DEFAULT_OPT
that does not work as there is no preserved position for appending--no-sort
in thefuzzback.sh
. I think this feature would be helpful if it could be added. Thanks.The text was updated successfully, but these errors were encountered: