Closed amano-kenji closed 1 month ago
This describes the behavior I mentioned.
No, this is by design. If you first deselect and then cancel the find, it would mean that every time a user cancels find, they have to give up the list of files they've already selected.
Introducing a cancel stack doesn't make sense to me either because it would break the following workflow:
f
to filter, then type a keyword like "a" to list all files containing "a".Space
to select some files.Esc
to exit the filter mode and return to the original file list - but since your last action was selecting files, it actually does a deselect instead of going back to the file list.If you want to change their order, please create a plugin to do that; here's an example https://github.com/sxyazi/yazi/pull/1042#issuecomment-2113994116.
Also, if you just want to cancel the find when entering or leaving a directory, you can simply rebind h
and l
:
{ on = "h", run = ["leave", "escape --find"], desc = "Go back to the parent directory" },
{ on = "l", run = ["enter", "escape --find"], desc = "Enter the child directory" },
Closing as it's the expected behavior
Okay.
I'm going to lock this issue because it has been closed for 30 days. ⏳ This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please file a new issue and complete the issue template so we can capture all the details necessary to investigate further.
What system are you running Yazi on?
Gentoo Linux
What terminal are you running Yazi in?
foot 1.16.2
yazi --debug
outputDid you try the latest nightly build to see if the problem got fixed?
No.
Describe the bug
I find a directory with
/
, enter it, and select a few files with space.Then, I press
esc
to cancel selection. However,find
is cancelled before selection is cancelled.This behavior was puzzling to me.
Perhaps, should there be a cancel stack that cancels the latest action first?