signify_sign_overwrite not behaving as expected.

[mhinz]

signify_sign_overwrite not behaving as expected.

[mhinz]

Hmm, you're right. I'm looking into it.

[kid-icarus]

Thanks for taking a look at this!

I just pulled, and this is what I'm experiencing:

If I edit a line with an existing syntax error and it still has an error, I only see the syntastic sign.

I'm expecting to see both the syntastic sign and the signify sign telling me that the line has an error and it has been modified.

Is it only possible to have one sign at a time?

[mhinz]

Yup, you can define several signs for the same line, but only one sign will be shown.

Thus there is g:signify_sign_overwrite that lets Vim know if you prefer seeing either the Signify or Syntastic signs if both are placed on the same line.

[kid-icarus]

Ok, wishful thinking I suppose :) Thanks for the prompt response!

On Sun, Apr 07, 2013 at 08:16:05AM -0700, Marco Hinz wrote:

Yup, you can define several signs for the same line, but only one sign will be shown.

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[jumski]

I just installed signify and I am experiencing this problem.
g:signify_sign_overwrite is set to 0 and still it overwrites syntastic error indicator.

When I save file i see sytastics indicator blink, immediately overwritten by a + sign.

Any ideas what could be wrong?

[mhinz]

I'm looking into it!

[jumski]

Just updated all bundles and still same behaviour.
Thanks in advance:)

[mhinz]

Hmm, funny. For me it works the other way around.

BTW, what features of syntastic do you use? I actually plan to add a similar functionality to Sy.

[jumski]

Sorry, didnt saw your quiestion (it was truncated in email notification to the first line).
I use syntastic defaults with a little tweak in form of:

let g:syntastic_mode_map = { 'mode': 'passive',
                             \ 'active_filetypes': ['ruby', 'erb', 'javascript', 'coffee'],
                             \ 'passive_filetypes': [] }

Regarding the bug: do you use vundle/neo_bundle in your vimrc?
In mine, syntastic is declared before signify, maybe you have it ordered differently and thats why?

[mhinz]

In the meantime I did some commits that solved the problem for me. I can enable/disable sign overwriting without problems now. I assume you pulled the latest changes, of course. :)

What's the output of :au BufWritePost? It should look similar to this, especially the order:

syntastic  BufWritePost
    *         call s:UpdateErrors(1)
signify  BufWritePost
    *         call sy#start(g:sy_path)

[jumski]

This is what i have:

syntastic  BufWritePost
    *         call s:UpdateErrors(1)
shebang_chmod  BufWritePost
    *         unlet! b:brand_new_file
              if exists('b:chmod_post') && executable('chmod') |   silent! execute '!chmod '.b:chmod_post.' "<afile>"' |   unlet b:chmod
_post | endif
signify  BufWritePost
    *         call sy#start(g:sy_path)
gzip  BufWritePost
    *.gz      call gzip#write("gzip")
    *.bz2     call gzip#write("bzip2")
    *.Z       call gzip#write("compress -f")
    *.lzma    call gzip#write("lzma -z")
    *.xz      call gzip#write("xz -z")
PowerlineMain  BufWritePost
    */autoload/Powerline/Colorschemes/*.vim
              :PowerlineReloadColorscheme
BufWritePost
    *         unlet! b:statusline_trailing_space_warning

Ordes is ok i guess?

[mhinz]

And you're really using the latest commit, right? (Sorry that I keep asking.) At the time of writing this is fcfb40c.

Because I just can't reproduce it. Neither with Vim nor gVim. I also removed all syntastic variables from my vimrc and used the g:syntastic_mode_map you gave above. And I tried it with one of the active filetypes, Ruby in my case.

The order is correct, because autocmds get executed in the order they were installed. Thus syntastic has to run first, so Sy can act on its signs.

Personally I'm not using any advanced plugin manager (neobundle, VAM etc.) If you have some spare time.. could you try using pathogen with Sy being the only plugin? I just want to rule out the interference of other plugins.