search

mhinz / vim-signify

:heavy_plus_sign: Show a diff using Vim its sign column.
MIT License
2.7k stars 103 forks source link

Signify doesn't show SVN code status in sign column #335

Closed yehudat closed 3 years ago

yehudat commented 4 years ago

Version: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 21 2016 17:10:26) Included patches: 1-207, 209-629 Doesn't work: set signcolumn=yes "or "yes" :!svn diff - works :SyDebug - "Not an editor command" :echo SignifyDebugListActiveBuffers() - show the changes monitored by the plugin. It seems to be an issues of the presentation.

jamessan commented 4 years ago

:SyDebug

The command is :SignifyDebug, however as described in README.md you need at least Vim 8.0.902 to use the master branch. If you're stuck with an older Vim, you should run from the legacy branch.

yehudat commented 4 years ago

Hi, Thanks for the reply. Would you send me a link to the legacy branch? I don’t see it on GitHub. I’m stuck with VIM7.4 :(

Best regards, YT

On 18 May 2020, at 4:15, James McCoy notifications@github.com wrote:

 :SyDebug

The command is :SignifyDebug, however as described in README.md you need at least Vim 8.0.902 to use the master branch. If you're stuck with an older Vim, you should run from the legacy branch.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

jamessan commented 4 years ago

Would you send me a link to the legacy branch?

Hmm, I guess the README is wrong. The pre-async code was kept.

In that case, can you post the output of :verbose w for a file that isn't displaying signs properly?

yehudat commented 4 years ago

Would you send me a link to the legacy branch?

Hmm, I guess the README is wrong. The pre-async code was kept.

In that case, can you post the output of :verbose w for a file that isn't displaying signs properly?

yehudat commented 4 years ago

I ran verbose w and it prints: “dir_name/file_name Line, Column written”

I use VIM8.1 now

jamessan commented 3 years ago

If you're still seeing this issue, could you run vim -V1 some_file and then show the output of :filter /\[sy/ messages?

mhinz commented 3 years ago

It was not just an old Vim version, but SignifyDebugListActiveBuffers() was removed 8 years ago, so the plugin was heavily out-of-date.

I also see that you switched to gitgutter in the meanwhile, so there probably won't be much activity in here anyway.

Thanks anyway. Closing!

yehudat commented 3 years ago

Hi, Not sure, what you are suggesting. Is there any solution available?

Regards, Yehuda Tsimanis

On 1 Apr, 2021, at 21:36, Marco Hinz @.***> wrote:

Closed #335 https://github.com/mhinz/vim-signify/issues/335.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/mhinz/vim-signify/issues/335#event-4542822987, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMC7L75NOVMGEYCJXC7NQMTTGS4MRANCNFSM4LUCJFJQ.