Question 1

How to install nvim-scissors with lazy.nvim?

Accepted Answer

Add the plugin to your lazy.nvim config with the snippetDir set to your snippet folder path, and ensure your snippet engine points to the same directory. Example configuration is provided in the README for seamless setup.

Question 2

Can I use nvim-scissors with friendly-snippets?

Accepted Answer

No, direct editing is unsupported because friendly-snippets updates would overwrite changes. However, you can copy individual snippet files to your own folder and edit them there, as explained in the Cookbook.

Question 3

nvim-scissors vs manually editing JSON files: which is better?

Accepted Answer

nvim-scissors automates JSON handling and provides a UI, making it faster and less error-prone for managing snippets. Manual editing is only better if you prefer raw JSON or use unsupported formats, as the plugin locks you into the VS Code format.

Question 4

How to create a snippet from a visual selection in Neovim?

Accepted Answer

In visual mode, use the addNewSnippet function with a keymap; it prefills the snippet body with the selection. For LuaSnip, enable store_selection_keys and use $TM_SELECTED_TEXT in the snippet body, as detailed in the Cookbook.

Question 5

Does nvim-scissors support auto-triggered snippets?

Accepted Answer

Not directly in the UI, but it preserves custom keys like 'luasnip' in JSON files. You need to add auto-trigger settings manually in the file using the openInFile keymap, as mentioned in the FAQ for LuaSnip users.

Question 6

What if I don't have Telescope or fzf-lua installed?

Accepted Answer

nvim-scissors falls back to vim.ui.select for snippet selection, but this lacks search and preview capabilities. It's recommended to install a picker for a better experience, as noted in the requirements section.

nvim-scissors

What is nvim-scissors?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions