Question 1

How do I install YankBank with lazy.nvim?

Accepted Answer

Add it as a plugin in your lazy.nvim config, include sqlite.lua as a dependency if using persistence, and call require('yankbank').setup() with your options. The README provides detailed examples for both persistent and non-persistent setups.

Question 2

YankBank vs nvim-neoclip: which is better?

Accepted Answer

YankBank focuses on minimalism and SQLite-based persistence, while nvim-neoclip offers more features like telescope integration and macro support. Choose YankBank for lightweight history with session saving; pick nvim-neoclip for broader functionality and ecosystem integration.

Question 3

Does YankBank work with Telescope?

Accepted Answer

Not currently; the README lists Telescope integration as a potential improvement. For now, it only supports snacks.nvim as an alternative picker, so users relying on Telescope may need to wait or use alternatives.

Question 4

How to clear the YankBank database?

Accepted Answer

Use the :YankBankClearDB command in Neovim, or manually delete the SQLite database file located in the plugin's install directory or as specified by the db_path option in your configuration.

Question 5

Can YankBank save yanks after closing Neovim?

Accepted Answer

Yes, by enabling persistence with persist_type = 'sqlite' in the setup, it uses SQLite to store yank history across sessions, ensuring your clipboard entries are preserved even after restarting Neovim.

Question 6

How to integrate YankBank with snacks.nvim?

Accepted Answer

Set pickers.snacks = true in your setup options, and then you can open the menu using :YankBankSnacks or via the snacks.nvim API like Snacks.picker.yankbank(), as described in the usage section.

yankbank-nvim

What is yankbank-nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions