How do I install YankBank with lazy.nvim?

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.

YankBank vs nvim-neoclip: which is better?

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.

Does YankBank work with Telescope?

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.

How to clear the YankBank database?

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.

Can YankBank save yanks after closing Neovim?

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.

How to integrate YankBank with snacks.nvim?

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.

Open-Awesome

yankbank-nvim

MITLuav1.3.0

A Neovim plugin that tracks yank and deletion history, providing a quick-access popup menu with optional session persistence.

GitHub

124 stars8 forks0 contributors

What is yankbank-nvim?

YankBank is a Neovim plugin that maintains a history of yanks and deletions, allowing users to quickly access and paste previous clipboard entries via a popup menu. It addresses the limitation of Neovim's default clipboard handling by storing multiple entries and offering optional persistence across sessions.

Target Audience

Neovim users who frequently copy and paste code or text and need reliable access to their clipboard history without switching contexts.

Value Proposition

Developers choose YankBank for its lightweight design, session persistence via SQLite, and seamless integration with Neovim's workflow, providing a straightforward solution to clipboard management without complex dependencies.

Overview

Neovim plugin improving access to clipboard history

Use Cases

Best For

Recovering recently deleted or yanked text in Neovim
Managing multiple clipboard entries during coding sessions
Pasting text copied from external applications into Neovim
Maintaining clipboard history across Neovim restarts
Customizing yank and paste keybindings for efficiency
Integrating clipboard history with other Neovim pickers like snacks.nvim

Not Ideal For

Users requiring system-wide clipboard management across multiple applications
Developers heavily reliant on Telescope or fzf for all navigation, as YankBank lacks native integration
Minimalist Neovim configs aiming to avoid additional dependencies like SQLite

Pros & Cons

Pros

Lightweight Startup

Initializes with minimal footprint and lazy loads, adding less than 1ms to startup time as highlighted in the README's best practices section.

Cross-Source Clipboard Sync

With focus_gain_poll enabled, it automatically detects and adds text copied from external apps like browsers to the yank history upon refocusing Neovim.

Session-Wide Persistence

Uses SQLite to save yank history across Neovim sessions via persist_type option, preventing data loss between editing sessions as recommended in the setup.

Flexible Keybinding Customization

Supports rebinding all popup actions through a configurable keymaps table, allowing users to tailor navigation, pasting, and closing to their workflow.

Cons

Limited Picker Ecosystem

Only integrates with snacks.nvim out of the box; popular alternatives like Telescope or fzf are listed as potential improvements but not yet implemented.

SQLite Dependency Overhead

Requires adding sqlite.lua as a dependency for persistence, complicating setup and potentially introducing compatibility or performance issues for some users.

Unstable API Surface

The API is marked as work-in-progress in the README, meaning it may lack features, have breaking changes, or be undocumented for advanced use cases.

Frequently Asked Questions

Related Projects

nvim-autopairs

autopairs for neovim written in lua

Stars4,066

Forks141

Last commit2 months ago

nvim-treesitter-context

Show code context

Stars3,215

Forks236

Last commit2 months ago

zen-mode.nvim

🧘 Distraction-free coding for Neovim

Stars2,149

Forks76

Last commit8 months ago

nvim-ts-autotag

Use treesitter to auto close and auto rename html tag

Stars2,104

Forks109

Last commit3 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub