Question 1

How do I set up hunk navigation in unified.nvim?

Accepted Answer

You need to manually map keys using the navigation API. For example, add `vim.keymap.set('n', ']h', function() require('unified.navigation').next_hunk() end)` to your Neovim config to jump to the next hunk, as shown in the README's navigation section.

Question 2

unified.nvim vs gitsigns.nvim for Git diffs in Neovim?

Accepted Answer

unified.nvim focuses on inline unified diffs with a file tree and optional snacks integration, while gitsigns.nvim provides gutter signs and hunk navigation without a tree view. Choose unified.nvim for integrated diff viewing with a sidebar, or gitsigns.nvim for a lighter, sign-based approach.

Question 3

Can I use unified.nvim without snacks.nvim?

Accepted Answer

Yes, snacks.nvim is optional. The default file tree backend works without it, but you'll miss features like built-in diff previews and staging in the picker, as detailed in the Snacks Integration section.

Question 4

How to show diffs against a specific branch in unified.nvim?

Accepted Answer

Use the command `:Unified origin/main` or any commit reference like a branch name. With snacks integration, use `:Unified -s origin/main` for the enhanced picker, as explained in the commands section.

Question 5

Does unified.nvim support staging individual lines or only hunks?

Accepted Answer

It supports hunk-level actions only. You can stage, unstage, or revert entire hunks, but not individual lines without modifying the hunk patch, based on the hunk actions API description.

Question 6

How to disable auto-refresh in unified.nvim?

Accepted Answer

Set `auto_refresh = false` in the configuration table passed to `setup()`. This prevents the diff view from updating automatically as you edit, which can help with performance in large files.

unified.nvim

What is unified.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions