-
Notifications
You must be signed in to change notification settings - Fork 33
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 support for history isearch #49
Comments
Let me know what you think. |
|
That's intended, and indeed in the general case only one recursion level is exited. |
I see, nice! |
Excellent!! Thank you, this works really well. |
True; it's arguable either way whether this makes sense or not. (Another interesting question is "should the selected candidate from history selection be itself added to history, and if so which one?" Currently the answer is that we add it to |
Good question, I think we should let bind |
Okay, that's reasonable. Want to make a pull request for that? |
Sure, just has to wait a few days probably. |
Done #72 |
Ignore selection side effects for history selection See discussion in #49. Also, if not within Selectrum insert result. This allows inserting elements into minibuffer for other minibuffer contexts like `eval-expression` and `shell-command` where you don't want necessarily exit with the result but insert it. Co-Authored-By: Radon Rosborough <radon.neon@gmail.com>
Incremental history search is very powerful, and it would be great if Selectrum supports it. So for example,
C-x C-f
would start a Selectrum-enabled file dialog, andC-r
would search throughfile-name-history
(or whichever history variable is appropriate for the given command). It would be especially great if the incremental search candidates could be shown in the Selectrum candidate narrowing display.The text was updated successfully, but these errors were encountered: