Workbench › List: Keyboard Navigation settings polish

[isidorn]

1. Explain better in setting value description what each setting does.
2. Filled Settings search does not search within values #66893. In case that does not get fixed consider adding word "filter" to the settings description

[isidorn]

workbench.list.keybaordNavigation: Controls the keyboard navigation style for lists and trees in the workbench. Can be simple, highlight and filter.
simple: Simple keyboard navigation focuses elements which match the keyboard input. Matching is done only on prefixes.
highlight: Highlight keyboard navigation highlights elements which match the keyboard input. Further up and down navigation will traverse only the highlighted elements.
filter: Filter keyboard navigation will filter out and hide all the elements which do not match the keyboard input.

fyi @weinand @bpasero on potential ideas for better wording

[bpasero]

I find the name keybaordNavigation weird as setting, to me this implies normal navigation without filtering. Should it not rather be workbench.list.filtering? That is the setting name I would look out for when caring about filtering in trees.

[joaomoreno]

@bpasero When the setting is set to highlight, there's no filtering at all.

[bpasero]

maybe workbench.list.search? searchNavigation?

[joaomoreno]

When it's set to simple, there's no search, only navigation.

[isidorn]

Note that the feature request which got 300+ upvotes had the following key words:
Navigate, explorer, typing. This means that a lot of people could find it in github search easily
#10026

Due to that I like that we use the word navigation to describe the setting
workbench.list.keyboardNavigation or workbench.list.typeToNavigate would work for me

The only thing I would do is add the world explorer in the setting description, so people that search for navigation and explorer actually get this setting.

[a-eid]

I used to navigate up and down with j and k, after the latest update 1.31 it doesn't work any more, none of the options give what I want. is there a way to revert to the way it used to act before the update?

[bpasero]

@a-eid are you using any extension for those keybindings or are they custom assigned by you?

[a-eid]

@bpasero I use VSCodeVim.