You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there is a long commit message, it overwrites the text of the file, as opposed to being cut off.
Neovim version
0.9.1
Operating system and version
macOS Ventura
Expected behavior
The commit message to be cut off, perhaps with ellipsis or the likes. At the very least, let the file's text to take precedence.
Actual behavior
A file with the follow contents:
The quick brown fox jumps over the lazy dog.
Committed with:
$ git commit -m "this is a very very very long git commit message that happens to be very long, as described"
Shows as such:
Minimal config
forname, urlinpairs{
gitsigns='https://github.com/lewis6991/gitsigns.nvim',
-- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
} dolocalinstall_path=vim.fn.fnamemodify('gitsigns_issue/'..name, ':p')
ifvim.fn.isdirectory(install_path) ==0thenvim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
endvim.opt.runtimepath:append(install_path)
endrequire('gitsigns').setup{
debug_mode=true, -- You must add this to enable debug messages-- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUEcurrent_line_blame=true,
current_line_blame_opts= {
virt_text_pos='right_align',
},
}
-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
Steps to reproduce
Open a git repository with a long commit message. E.g.:
$ mkdir /tmp/test
$ cd /tmp/test
$ git init
$ echo"The quick brown fox jumps over the lazy dog.">hello
$ git add hello
$ git commit -m "this is a very very very long git commit message that happens to be very long, as described"
nvim --clean -u minimal.lua /tmp/test/hello
Make the window smaller, if need be.
Gitsigns debug messages
signs.init: Using vimfn signs
dprintf: Deriving GitSignsAdd from DiffAdd
dprintf: Deriving GitSignsChange from DiffChange
dprintf: Deriving GitSignsDelete from DiffDelete
dprintf: Deriving GitSignsChangedelete from GitSignsChange
dprintf: Deriving GitSignsTopdelete from GitSignsDelete
dprintf: Deriving GitSignsUntracked from GitSignsAdd
dprintf: Deriving GitSignsAddNr from GitSignsAdd
dprintf: Deriving GitSignsChangeNr from GitSignsChange
dprintf: Deriving GitSignsDeleteNr from GitSignsDelete
dprintf: Deriving GitSignsChangedeleteNr from GitSignsChangeNr
dprintf: Deriving GitSignsTopdeleteNr from GitSignsDeleteNr
dprintf: Deriving GitSignsUntrackedNr from GitSignsAddNr
dprintf: Deriving GitSignsAddLn from DiffAdd
dprintf: Deriving GitSignsChangeLn from DiffChange
dprintf: Deriving GitSignsChangedeleteLn from GitSignsChangeLn
dprintf: Deriving GitSignsUntrackedLn from GitSignsAddLn
dprintf: Deriving GitSignsStagedAdd from GitSignsAdd
dprintf: Deriving GitSignsStagedChange from GitSignsChange
dprintf: Deriving GitSignsStagedDelete from GitSignsDelete
dprintf: Deriving GitSignsStagedChangedelete from GitSignsChangedelete
dprintf: Deriving GitSignsStagedTopdelete from GitSignsTopdelete
dprintf: Deriving GitSignsStagedAddNr from GitSignsAddNr
dprintf: Deriving GitSignsStagedChangeNr from GitSignsChangeNr
dprintf: Deriving GitSignsStagedDeleteNr from GitSignsDeleteNr
dprintf: Deriving GitSignsStagedChangedeleteNr from GitSignsChangedeleteNr
dprintf: Deriving GitSignsStagedTopdeleteNr from GitSignsTopdeleteNr
dprintf: Deriving GitSignsStagedAddLn from GitSignsAddLn
dprintf: Deriving GitSignsStagedChangeLn from GitSignsChangeLn
dprintf: Could not derive GitSignsStagedDeleteLn
dprintf: Deriving GitSignsStagedChangedeleteLn from GitSignsChangedeleteLn
dprintf: Could not derive GitSignsStagedTopdeleteLn
dprintf: Deriving GitSignsAddPreview from DiffAdd
dprintf: Deriving GitSignsDeletePreview from DiffDelete
dprintf: Deriving GitSignsCurrentLineBlame from NonText
dprintf: Deriving GitSignsAddInline from TermCursor
dprintf: Deriving GitSignsDeleteInline from TermCursor
dprintf: Deriving GitSignsChangeInline from TermCursor
dprintf: Deriving GitSignsAddLnInline from GitSignsAddInline
dprintf: Deriving GitSignsChangeLnInline from GitSignsChangeInline
dprintf: Deriving GitSignsDeleteLnInline from GitSignsDeleteInline
dprintf: Deriving GitSignsDeleteVirtLn from DiffDelete
dprintf: Deriving GitSignsDeleteVirtLnInLine from GitSignsDeleteLnInline
dprintf: Deriving GitSignsVirtLnum from GitSignsDeleteVirtLn
attach(1): Attaching (trigger=setup)
run_job: git --version
run_job: git --no-pager --literal-pathspecs -c gc.auto=0 config user.name
run_job: git --no-pager --literal-pathspecs -c gc.auto=0 rev-parse --show-toplevel --absolute-git-dir --abbrev-ref HEAD
run_job: git --no-pager --literal-pathspecs -c gc.auto=0 --git-dir /Users/mariellh/t/.git -c core.quotepath=off ls-files --stage --other
s --exclude-standard --eol /Users/mariellh/t/hello
watch_gitdir(1): Watching git dir
run_job: git --no-pager --literal-pathspecs -c gc.auto=0 --git-dir /Users/mariellh/t/.git show :0:hello
update(1): updates: 1, jobs: 5
run_job: git --no-pager --literal-pathspecs -c gc.auto=0 --git-dir /Users/mariellh/t/.git blame --contents - -L 1,+1 --line-porcelain /U
sers/mariellh/t/hello
cli.run: Running action 'debug_messages' with arguments {}
The text was updated successfully, but these errors were encountered:
Description
When there is a long commit message, it overwrites the text of the file, as opposed to being cut off.
Neovim version
0.9.1
Operating system and version
macOS Ventura
Expected behavior
The commit message to be cut off, perhaps with ellipsis or the likes. At the very least, let the file's text to take precedence.
Actual behavior
A file with the follow contents:
Committed with:
$ git commit -m "this is a very very very long git commit message that happens to be very long, as described"
Shows as such:
![image](https://private-user-images.githubusercontent.com/19861299/265676229-ae466335-e362-49a6-a383-314cc85f65d3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTg2OTU2NjQsIm5iZiI6MTcxODY5NTM2NCwicGF0aCI6Ii8xOTg2MTI5OS8yNjU2NzYyMjktYWU0NjYzMzUtZTM2Mi00OWE2LWEzODMtMzE0Y2M4NWY2NWQzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjE4VDA3MjI0NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQ4YzFiYzU2MmFlYmMxNDI5OGM0YzMxYmYxNWQ3ODhjYmZhZWVhNTgzOGFjMjY5ZDBiZjRlYjlkNjIzOWJjMjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.FnXGQbtiwBKxWNetPip3JxpTRufQ-I0UznG3U6mBKGY)
Minimal config
Steps to reproduce
nvim --clean -u minimal.lua /tmp/test/hello
Gitsigns debug messages
The text was updated successfully, but these errors were encountered: