Question 1

How do I set up cmdbuf.nvim to replace the default q: mapping?

Accepted Answer

Map a key in your Neovim config using `vim.keymap.set`, like in the README example, to call `require('cmdbuf').split_open` with the desired height, such as binding 'q:' to open a command buffer in a split window.

Question 2

What's better, cmdbuf.nvim or the built-in command-line window?

Accepted Answer

cmdbuf.nvim is better for flexibility and customization, as it uses normal buffers for editing and supports multiple command types, while the built-in version is simpler but restrictive in navigation and window behavior. Choose based on your need for control versus out-of-the-box functionality.

Question 3

How can I filter command history lines in cmdbuf.nvim?

Accepted Answer

Use the Lua API within an autocmd, as shown in the README, to programmatically filter buffer lines—for instance, by iterating over lines with `vim.iter` and removing specific commands like 'q' from the history.

Question 4

Does cmdbuf.nvim work with search commands like q/ and q??

Accepted Answer

Yes, it supports search commands with types 'vim/search/forward' and 'vim/search/backward', and you can map keys similarly to the default, as demonstrated in the examples for 'q/' and 'q?' alternatives.

Question 5

How to configure cmdbuf.nvim for Lua command history?

Accepted Answer

Map a key, such as 'ql', to open a buffer with type 'lua/cmd' using `require('cmdbuf').split_open` and specifying the type in options, allowing you to edit and execute Lua command history in a normal buffer.

cmdbuf.nvim

What is cmdbuf.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions