Question 1

How do I set up keybindings for Hop.nvim in Neovim?

Accepted Answer

You need to define key mappings manually in your config file. For example, use vim.keymap.set in Lua to map keys to Hop functions like hop.hint_char1, as shown in the README's keybindings section.

Question 2

Hop.nvim vs leap.nvim: which should I choose?

Accepted Answer

Hop.nvim uses hint sequences for navigation, offering labeled targets for precise jumps, while leap.nvim employs a search-based incremental approach. Choose Hop if you prefer visual hints; opt for leap for a more minimal, keyboard-driven experience.

Question 3

Can Hop.nvim work with Vim operators like delete or change?

Accepted Answer

Yes, Hop integrates with operators such as v, d, c, y. After initiating a jump, you can combine it with an operator to select, delete, change, or yank text up to the target position, enhancing editing efficiency.

Question 4

How to customize the hint keys in Hop.nvim?

Accepted Answer

During setup, specify the 'keys' option in the configuration. For instance, in the setup function, set keys to a string like 'etovxqpdygfblzhckisuran' to define the label dictionary used for hints.

Question 5

Does Hop.nvim support navigation across multiple windows?

Accepted Answer

Yes, it has multi-window support with commands like :HopWordMW, allowing you to jump to targets in other Neovim windows seamlessly, which is useful for split-screen editing.

Question 6

What is the performance impact of using Hop.nvim on large files?

Accepted Answer

While optimized for speed, annotating hints in very large buffers might cause slight rendering delays or visual clutter. However, it's generally efficient for typical code files, and performance issues are uncommon.

hop.nvim

What is hop.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions