-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] win options clobbered (winhl
), not set (winblend
)
#515
Labels
bug
Something isn't working
Comments
Idk why (it fires on TabEnter), but I guess adding |
This also doesn't work: nvim --clean +"lua require('diffview').setup { commit_log_panel = { win_config = { winopts = { winblend = 10, } } } }" |
tmillr
changed the title
[Bug] window options get clobbered (e.g.
[Bug] win options clobbered (Jul 1, 2024
winhl
)winhl
), not set (winblend
)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Leaving and coming back to the diffview tab, or simply just revisiting one of the diffs (buffers), resets/clobbers all of my
winhl
customizations. Is there any reason why this plugin is dynamically changing/resetting options onTabLeave
, or, when revisiting a previously-viewed buffer (especially given the fact that the window ids remain the same)? This is silly and unexpected behavior imo. How else can I customizewinhl
? Right now I'm using aDiffviewDiffBufRead
autocmd (because setting win opts or config via this plugin seems to be only supported for "panels"?).I guess in the meantime I need to choose a different autocmd, or force my highlights with a window namespace.
Expected behavior
winhl
or any other list-like options that this plugin sets (you need to share, or allow me a way to accomplish this via other means, lol).Actual behavior
See Description
Steps to reproduce
Health check
Likely irrelevant, but here it is:
Log info
n/a
Neovim version
Operating system and version
macOS 14.2.1
Minimal config
Maybe related to: #457, #442
The text was updated successfully, but these errors were encountered: