Question 1

How do I set up pretty_hover with blink.cmp?

Accepted Answer

Add the provided Lua snippet to your blink.cmp configuration, which uses the parser module to format documentation values before display, ensuring enhanced completion docs. See the Integration section for details.

Question 2

What are the limitations of pretty_hover's markdown styling?

Accepted Answer

It relies on Neovim's markdown renderer, which only supports basic stylers like `, *, and ```[language], preventing advanced combinations or nested formatting. This is explicitly mentioned in the Limitations part of the README.

Question 3

pretty_hover vs hover.nvim: which should I use?

Accepted Answer

Pretty_hover adds features like number conversion and customizable highlight groups, while hover.nvim might be simpler. Choose pretty_hover if you need these extras, but compare based on your styling needs and configuration preferences.

Question 4

How to customize highlight groups in pretty_hover?

Accepted Answer

Define custom highlight groups in the hl table of your configuration, specifying color and detectors, as shown in the default config example. This allows color-coding elements like errors or warnings in hover text.

Question 5

Does pretty_hover support multiple LSP servers?

Accepted Answer

Yes, with Neovim 0.11.0 or higher, you can enable the multi_server option to handle hover messages from multiple servers concurrently. Otherwise, this option is ignored, as noted in the Configuration.

Question 6

How to close the pretty_hover window?

Accepted Answer

You can close it by moving the cursor, pressing 'q' when focused, or calling require('pretty_hover').close() from a keymap. This is detailed in the usage section for flexibility.

pretty_hover

What is pretty_hover?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions