Confusing default behaviour for cmdline

[PowerUser64]

I'd like to share my thoughts on this, in hopes that others will chime in if they feel the same (or otherwise).

When I moved to blink, I customized the keybinds a lot. I use <C-jk> for menu navigation, <C-l> for confirm, and <C-h> for show/hide. It was not clear to me at first that the cmdline used different keybinds by default, and I thought it was just broken or not implemented for the longest time. Part of this was my own doing, for using such non-standard keybinds for the completion menu (and maybe for not RTFM on the cmdline soon enough), but this felt to me like something that doesn't seem to quite align with blink's design philosophy.

I'm wondering if maybe the cmdline mappings should have a preset for replicating the behavior of the insert mode completion menu that, if not enabled by default, gets mentioned in the docs in the keymap section with a message like, "If you want your keymap and other settings to apply to the cmdline, set cmdline = { preset = 'insert_fallback' }" (or something like that). I'm thinking this preset would also copy other things like completion.menu.auto_show. Such a preset would help prevent people from getting into a situation like my own where they've and set up custom behavior that they think is being used when it really isn't, so it looks broken.

Does anyone else have thoughts on this?

[soifou]

There is an opened issue for what you describe, see #1327. You could share your thoughts there for more visibility?

[PowerUser64]

Nice, thanks! I'll post there.

(also, 1327 .. almost 1337, cool)