-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Linematch, diffopt, and diffget/put not working as expected. #22696
Comments
@jwhite510. Do you know why this might be? |
@SeniorMars linematch with diffget looks like it's working as I'd expect. As the differences are more granular, the 'diffget' and 'diffput' operations The difference when it comes to 'diffget' and 'diffput' operations is that this
when you have the cursor in buffer 4 and call a :diffget from buffer 3, it is getting I believe the behaviour you are looking for can be obtained by first visually like this: :'<,'>diffget ... so that diffget will be applied to each diff (all 6) in the visual selection when you disable linematch, the entire thing is one diff, and diffget will get |
because of this issue for the nvimdiff neovim/neovim#22696
Problem
Linematch and diffget do not work correctly together. I use diffget to resolve merge conflicts, and with this new diffopt option, I'm not getting the expected behavior.
Since merging is a complicated mess, I tried to record what I mean in a 17second gif:
Steps to reproduce
Generally:
nvim -d
I see that diffget does not resolve a merge conflict as I expected.
Expected behavior
With the default options of diffopt, using diffget with
nvim -d
, I can resolve merge conflicts, but not with linematch appened to diffopt.Neovim version (nvim -v)
NVIM v0.9.0-dev-2446+g995196c61-dirty
Vim (not Nvim) behaves the same?
No, as linematch is not implmented yet: vim/vim#9661
Operating system/version
macOS 13.2.1
Terminal name/version
kitty
$TERM environment variable
xterm-kitty
Installation
brew
related to #14537 and perhaps #20931
The text was updated successfully, but these errors were encountered: