local foo = 1
<<<<<<< HEAD
local value = 5 + 7
print(value)
print(string.format("value is %d", value))
||||||| c59b690
local value = 1 + 1
=======
local value = 1 - 1
>>>>>>> new_branch
print(foo, value)
If the cursor is on the line >>>>>>> new_branch and you run a GitConflictChoose* cmd or call the require("git-conflict").choose() function, nothing will happen. If the cursor is on the line above the last line, it will work as expected.
Interestingly, if the cursor is on the line before the change (local foo = 1), running GitConflictChoose* will work, when I would not expect it to. This leads me to believe this is an off-by-one bug.
For example, with the following change:
If the cursor is on the line
>>>>>>> new_branch
and you run aGitConflictChoose*
cmd or call therequire("git-conflict").choose()
function, nothing will happen. If the cursor is on the line above the last line, it will work as expected.Interestingly, if the cursor is on the line before the change (
local foo = 1
), runningGitConflictChoose*
will work, when I would not expect it to. This leads me to believe this is an off-by-one bug.See: https://github.com/akinsho/git-conflict.nvim/issues/48#issuecomment-2131531276