Question 1

How to set up guard.nvim for automatic formatting on save?

Accepted Answer

Set vim.g.guard_config.fmt_on_save = true in your Neovim config, then register formatters per filetype using ft('filetype'):fmt('tool'), such as ft('lua'):fmt('stylua'). This enables formatting whenever you save a buffer.

Question 2

guard.nvim vs null-ls: which should I use?

Accepted Answer

Guard.nvim focuses on async performance and a minimal API for lightweight customization, ideal for speed-centric workflows. Null-ls offers more built-in sources and integrations, but guard.nvim is better for users who prefer fine-grained control over external tools.

Question 3

Does guard.nvim work with LSP formatting?

Accepted Answer

Yes, it can integrate LSP formatting by setting lsp_as_default_formatter = true in the config, but this is optional and not enabled by default, allowing it to complement or replace LSP-based formatting.

Question 4

How to disable auto linting in guard.nvim?

Accepted Answer

Set vim.g.guard_config.auto_lint = false in your configuration, or use the Guard disable-lint command per buffer to turn off automatic linting for specific files.

Question 5

Can I use guard.nvim with custom shell commands for linting?

Accepted Answer

Yes, define a custom linter using the lint function with a table specifying cmd and args, similar to formatters, allowing integration of any command-line tool that outputs diagnostics.

Question 6

What are the performance impacts of guard.nvim?

Accepted Answer

Guard.nvim is designed to be lightweight and async, minimizing performance hits by running tools in the background, but frequent linting with tools like codespell on all files (*) might add overhead depending on project size.

guard.nvim

What is guard.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions