A Neovim plugin to help you work out WTF that diagnostic means!

wtf.nvim provides faster and more efficient ways of working with the buffer line's diagnostic messages by redirecting them to tools straight from Neovim.

Works with any language that has LSP support in Neovim.

Use the power of ChatGPT to provide you with explanations and solutions of how to fix hints, warnings and errors, custom tailored to the code responsible for them.

	Before	After
Python
Typescript

Why spend time typing out error messages when you can open them in Google, Stack Overflow and more, directly from Neovim?

Google	Duck Duck Go
Stack Overflow	Github Issues

In order to use the AI functionality, set the environment variable OPENAI_API_KEY to your openai api key (the search functionality will still work without it).

Install the plugin with your preferred package manager:

lazy.nvim:

{
	"piersolenski/wtf.nvim",
	dependencies = {
		"MunifTanjim/nui.nvim",
	},
  	opts = {},
	keys = {
		{
			"gw",
			mode = { "n" },
			function()
				require("wtf").ai()
			end,
			desc = "Debug diagnostic with AI",
		},
		{
			mode = { "n" },
			"gs",
			function()
				require("wtf").search()
			end,
			desc = "Search diagnostic with Google",
		},
	},
}

{
    -- Default AI popup type
    popup_type = "popup" | "horizontal" | "vertical",
    -- An alternative way to set your OpenAI api key
    openai_api_key = "sk-xxxxxxxxxxxxxx",
    -- ChatGPT Model
    openai_model_id = "gpt-3.5-turbo",
    -- Set your preferred language for the response
    language = "english",
    -- Any additional instructions
    additional_instructions = "Start the reply with 'OH HAI THERE'",
    -- Default search engine, can be overridden by passing an option to WtfSeatch 
    default_search_engine = "google" | "duck_duck_go" | "stack_overflow" | "github",
}

wtf.nvim works by sending the line's diagnostic messages along with contextual information (such as the code and filetype) to various differing sources you can configure.

Whenever you have an error in an LSP enabled environment, invoke a wtf.nvim command on that line:

• Pretty TypeScript Errors
• backseat.nvim
• folke