I have the same question and would extend it to command history too.

Yeah, for some reason the arrows don't work in command mode anymore. I tried installing some very old versions of this plugin and still could not get it to work, so I assume an update to VSCode broke it, not this plugin. Trying to manually map the arrow keys don't work either, however, putting this in your keybindings is a mediocre fix:

    {
        "command": "vscode-neovim.history-up-cmdline",
        "key": "ctrl-p",
        "when": "neovim.mode == cmdline_normal"
    },
    {
        "command": "vscode-neovim.history-down-cmdline",
        "key": "ctrl-n",
        "when": "neovim.mode == cmdline_normal"
    },

I remember this working for me and I don't think it was too long ago. It no longer does, but that workaround did the trick for now. Thanks @theol0403!

It works also for me!. Thanks to @theol0403

@theol0403, thanks!
@asvetliakov, maybe made this shortcuts by default? By default <C-p> and <C-n> works in Neovim for search too.

If you could get arrows to work will be ideal. Muscle memory is hard to change. I have seen other vim integrations that even include a drop-down with the history, so moving up/down is easier.

VSCode started to disallow to remap <up>/<down> in quick pick. Blame vscode devs ! 👿 👿 👿

@asvetliakov Any thoughts on moving the command line to the VSCode status bar (the bottom bar in the ide)?

The VSCodeVim extension exposes the vim commandline in that bar - it shows what you're typing and allows you to navigate through history with arrow keys due to it. Could resolve this problem

@uladkasach It would be worth considering, and also solve a few other problems regarding quickpick's limitations (and support more bindings). However, the largest drawback is showing completions - any idea how that could be done?

@theol0403 VSCodeVim implemented this in https://github.com/VSCodeVim/Vim/pull/2758/files. Some asked for the ability to move it back (VSCodeVim/Vim#2773, VSCodeVim/Vim#3602) but I'd say : opening in quick open is one of the biggest cons transitioning from VSCodeVim to vscode-neovim so far.

Though, I think a really good approach to multiple buffers (#505) might lead to the most optimal, fully-featured command buffer. Maybe something leveraging horizontal splits. View: Toggle Split Editor In Group and View: Toggle Layout of Split Editor in Group can be used to make "borderless" splits of the same file, and microsoft/vscode#36700 (comment) implies there might be a way to do that using some custom view.

Still not fixed, waiting for

microsoft/vscode#196899

Fixed by #2001