Selecting the second buffer after filtering in ivy-switch-buffer leads to unintuitive buffer switching #513
Comments
I think it is related to this: #496 |
In an effort to scratch my own itch here, I've replaced use of So far it seems good but I'm going to run with this for a while to see if this fixes my issue without breaking anything else. |
abo-abo
added a commit
that referenced
this issue
Aug 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce, using ivy-switch-buffer to switch buffers:
todo.org
andtodo.org_archive
.todo.org
.*Messages*
.*scratch*
.ivy-switch-buffer
.todo
.Expected behavior:
todo.org
is first in Ivy's candidates list and is selected, since that was the most recent buffer with that string.Observed behavior:
todo.org
is first in Ivy's candidates, buttodo.org_archive
is the second and is the selected option, presumably becauseivy-switch-buffer
starts with the "other" buffer selected by default, which (AFAIK) is always the second option.Is there any way to get
ivy-switch-buffer
to select the most recent non-current buffer after filtering? I believe this behavior changed as of 79ffa67 (#484). Thanks!The text was updated successfully, but these errors were encountered: