Question 1

How to set up wtf.nvim with Ollama for local AI?

Accepted Answer

Set the provider to 'ollama' in your config and ensure Ollama is running locally; no external API key is needed, but you must have local models installed, as per the provider support for offline use.

Question 2

Can wtf.nvim fix all LSP errors automatically?

Accepted Answer

No, AI fixes are not always accurate and depend on the model and issue complexity. It's best for common diagnostics, but manual review is advised, as implied by the ability to add custom instructions for fixes.

Question 3

wtf.nvim vs null-ls for handling diagnostics?

Accepted Answer

wtf.nvim focuses on AI-powered explanation and fixing of existing LSP diagnostics, while null-ls generates diagnostics from linters and formatters. Use wtf.nvim for debugging and null-ls for broader code quality tools.

Question 4

Is wtf.nvim safe for proprietary code?

Accepted Answer

It sends code snippets to external AI services by default, posing privacy risks. For secure use, configure local providers like Ollama or avoid sending sensitive code, as highlighted in the provider setup with API keys.

Question 5

How to search diagnostic history with Telescope?

Accepted Answer

Install Telescope as a dependency, set the picker to 'telescope' in the config, and use :WtfGrepHistory to grep through chat history using Telescope's interface, as documented in the picker compatibility section.

Question 6

Does wtf.nvim work with any programming language?

Accepted Answer

Yes, it works with any language that has LSP support in Neovim, as it leverages Neovim's built-in LSP client to fetch diagnostic messages, regardless of file type.

wtf.nvim

What is wtf.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions