question: Integration toggle possible for mini.diff? #151

Closed
opened 2026-09-21 18:12:33 +00:00 by barrettruth · 2 comments
Owner

Original issue: barrettruth/diffs.nvim#357
Original author: HaleTom
Original date: 2026-05-17T10:39:55Z

Prerequisites

Neovim version

NVIM v0.12.2
Build type: RelWithDebInfo
LuaJIT 2.1.1774896198
Run "nvim -V1 -v" for more info

Operating system

Manjaro

Description

There appears to be a documentation inconsistency regarding integrations and conflicting plugins:

  • The README shows that integrations for several plugins (including fugitive, neogit, gitsigns, etc.) can be enabled via the vim.g.diffs.integrations config. However, plugins like mini.diff and diffview.nvim are listed as known conflicts.

  • For some conflicting plugins (like gitsigns), you can set gitsigns = true in integrations. However, there is no mention of an option like mini.diff = true. This raises a question:

Is there (or can there be) an integrations.mini.diff = true configuration, or is there another recommended way to manage this conflict?

  • If not, could you clarify the expected interaction or add an explicit note in the documentation about why mini.diff integration is not available, to avoid confusion?

This request is to clarify and improve the documentation regarding conflict/integration handling with mini.diff, and with other plugins listed as possibly incompatible.

Steps to reproduce

  1. Read the README regarding integrations (supported plugins via vim.g.diffs.integrations)
  2. Note that mini.diff is listed as conflicting, but not shown as a possible integration toggle
  3. Try to set vim.g.diffs = { integrations = { ['mini.diff'] = true } } in your config and observe behavior
  4. Attempt to use both plugins together and note issues or lack of integration
  5. Consult documentation for explicit guidance on handling this scenario

Health check

==============================================================================
diffs:                                                                    1 ⚠️

diffs.nvim ~
- ✅ OK Neovim 0.9.0+ detected
- ⚠️ WARNING vim-fugitive not detected (required for unified diff highlighting)
- libvscode_diff not found (optional, using native vim.diff fallback)

Minimal reproduction

See above context for a minimal setup that attempts to enable both diffs.nvim and mini.diff, and for observations about integration fields in the configuration.
> Original issue: barrettruth/diffs.nvim#357 > Original author: `HaleTom` > Original date: 2026-05-17T10:39:55Z ### Prerequisites - [x] I have searched [existing issues](https://github.com/barrettruth/diffs.nvim/issues) - [x] I have updated to the latest version ### Neovim version ```text NVIM v0.12.2 Build type: RelWithDebInfo LuaJIT 2.1.1774896198 Run "nvim -V1 -v" for more info ``` ### Operating system Manjaro ### Description There appears to be a documentation inconsistency regarding integrations and conflicting plugins: - The README shows that integrations for several plugins (including `fugitive`, `neogit`, `gitsigns`, etc.) can be enabled via the `vim.g.diffs.integrations` config. However, plugins like `mini.diff` and `diffview.nvim` are listed as known conflicts. - For some conflicting plugins (like `gitsigns`), you can set `gitsigns = true` in integrations. However, there is no mention of an option like `mini.diff = true`. This raises a question: **Is there (or can there be) an `integrations.mini.diff = true` configuration, or is there another recommended way to manage this conflict?** - If not, could you clarify the expected interaction or add an explicit note in the documentation about why `mini.diff` integration is not available, to avoid confusion? This request is to clarify and improve the documentation regarding conflict/integration handling with `mini.diff`, and with other plugins listed as possibly incompatible. ### Steps to reproduce 1. Read the README regarding integrations (supported plugins via `vim.g.diffs.integrations`) 2. Note that `mini.diff` is listed as conflicting, but not shown as a possible integration toggle 3. Try to set `vim.g.diffs = { integrations = { ['mini.diff'] = true } }` in your config and observe behavior 4. Attempt to use both plugins together and note issues or lack of integration 5. Consult documentation for explicit guidance on handling this scenario ### Health check ```text ============================================================================== diffs: 1 ⚠️ diffs.nvim ~ - ✅ OK Neovim 0.9.0+ detected - ⚠️ WARNING vim-fugitive not detected (required for unified diff highlighting) - libvscode_diff not found (optional, using native vim.diff fallback) ``` ### Minimal reproduction ```lua See above context for a minimal setup that attempts to enable both diffs.nvim and mini.diff, and for observations about integration fields in the configuration. ```
barrettruth 2026-09-21 18:12:33 +00:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

Original comment: barrettruth/diffs.nvim#357, comment 4471034261
Original author: barrettruth
Original date: 2026-05-17T14:45:55Z

I don't use mini.diff.

I can install and play around with it but my expectations of what a proper integration looks like are much likely to be worse than yours, a full on user.

Do you mind going into a bit of detail of whag you'd like to see, screenshots included?

Thanks for the issue.

> Original comment: barrettruth/diffs.nvim#357, comment 4471034261 > Original author: `barrettruth` > Original date: 2026-05-17T14:45:55Z I don't use mini.diff. I can install and play around with it but my expectations of what a proper integration looks like are much likely to be worse than yours, a full on user. Do you mind going into a bit of detail of whag you'd like to see, screenshots included? Thanks for the issue.
Author
Owner

Original comment: barrettruth/diffs.nvim#357, comment 4524018691
Original author: barrettruth
Original date: 2026-05-23T03:23:45Z

Closing due to lack of activity feel free to reopen.

> Original comment: barrettruth/diffs.nvim#357, comment 4524018691 > Original author: `barrettruth` > Original date: 2026-05-23T03:23:45Z Closing due to lack of activity feel free to reopen.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
barrettruth/diffs.nvim#151
No description provided.