Enable the ability to sort the which key

[taylo2allen]

Is your feature request related to a problem? Please describe

No response

Will you be willing to contribute this feature?

• Yes, I'll give it a shot

Describe the solution you'd like

In the yazi.toml add [which] that has the methods sort_by & sort_sensitive that allows you to sort the which menu.

Describe alternatives you've considered

One way for me to sort the which menu is to physically go to my keymap.toml and sort my keybinding definitions.

Additional context

No response

[sxyazi]

Sounds good to me. Does anyone want to give it a try?

[abhaysp95]

@taylo2allen I completed the rust basics and I have just started using Yazi. I would like to help. I want to understand few points for this issue:

• What is meant by sorting the which key ?
• Currently, sort_by & sort_sensitive option are under [manager]. What is wanted is to created a new table named [which] ?
• Can you kindly show the steps of what you are doing for 'alternatives' you mentioned

CC: @sxyazi

[sxyazi]

Thank you very much for the help! @abhaysp95

I'll wait for OP's reply and provide more detailed suggestions on how to implement it :)

[taylo2allen]

I have a lot of keykindings to move to different folders on my system for example:
`
{ on = [ "g", "C" ], exec = "cd ~/.config", desc = "GoTo: ~/.config" },
{ on = [ "g", "c", "b" ], exec = "cd ~/.config/xmobar", desc = "GoTo: ~/C/xmobar" },
{ on = [ "g", "c", "f" ], exec = "cd ~/.config/fish", desc = "GoTo: ~/C/fish" },
{ on = [ "g", "c", "q" ], exec = "cd ~/.config/qutebrowser", desc = "GoTo: ~/C/qutebrowser" },
{ on = [ "g", "c", "r" ], exec = "cd ~/.config/ranger", desc = "GoTo: ~/C/ranger" },
{ on = [ "g", "c", "x" ], exec = "cd ~/.config/xmonad", desc = "GoTo: ~/C/xmonad" },

`
in the code above I use "g", "c" as a leader key to go to all of the folders I have bookmarked in my .config folder. When I press the "g" key the whichkey menu pops up with the next possible keys you can press, I would like to sort the options for keybindings like "c", "b" to be shown first before "c", "x". The only way I found to sort the list of keybindings is to shift the definitions around in my keymap.toml file.

[abhaysp95]

@taylo2allen Okay. So this has nothing to do with sorting options present under [manager]. Got it.

• sort_by can only have "alphabetically" and "alphabetically (reverse)', right ? or do you have some more options in mind ?

@sxyazi I'm going through the source code, I'll try to implement it in the free time I get between my work. This is a nice project and looks like a fun way to get good with Rust.

[taylo2allen]

Thank you for taking a look @sxyazi @abhaysp95 I believe this would be possible to implement this feature with the sort function found in yazi-core/src/folder/sorter.rs instead of feeding two files into the sort fn you can pass two items in the list of possible keybindings before the text can be displayed on the screen.

[sxyazi]

I'm going through the source code, I'll try to implement it in the free time I get between my work. This is a nice project and looks like a fun way to get good with Rust.

Thanks.

I believe this would be possible to implement this feature with the sort function found in yazi-core/src/folder/sorter.rs instead of feeding two files into the sort fn you can pass two items in the list of possible keybindings before the text can be displayed on the screen.

No, it's a file-specific sorting, not applicable to keys, as keys don't have file-specific attributes like modification time, creation time, extension, etc., and they are also hard to share. Therefore, the simplest way is to directly invoke natsort function to sort.

We can add the sorting logic after

yazi/yazi-core/src/which/commands/show.rs

Lines 48 to 53 in b6f572e

	self.cands = KEYMAP
	.get(layer)
	.iter()
	.filter(|c| c.on.len() > 1 && &c.on[0] == key)
	.map(|c| c.into())
	.collect();

It's the only place that needs to change, with:

• sort_by (String): "key" or "description"
• sort_sensitive (Boolean): Whether sort case-sensitively

[abhaysp95]

@taylo2allen I have created the PR #662 . You can try to confirm the behaviour if it fits you

CC: @sxyazi

[github-actions]

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 open a new issue and complete the issue template so we can capture all the details necessary to investigate further.