Instead of using the sign id as the primary piece of data, store
information on a per-hunk granularity. A hunk has a start/end line as
well as a set of sign ids that have been placed within those lines.
This makes moving to the start of the next/previous hunk, as per the
behavior of the standard `]c`/`[c` bindings, pretty straight forward --
a simple filter to find relevant hunks, and then grab the first sign id.
Some VCS rely on an external diff tool, because they don't support the
-U0 flag natively. Most of the time that's the standard 'diff' utility.
But fritzophrenic was reporting that even a GNU diff won't always be
installed as 'diff', but e.g. as 'gnudiff' instead.
You can set the external diff tool now.
Closes#29.
People using themes for their terminal emulators that do a lot of
voodoo, could experience sign color problems because of the font being
bold by default.
Thus a new variable was introduced: g:signify_sign_weight.
Fixes#24.
Signs (from Syntastic in this case) were overwritten, although
g:signify_sign_overwrite was set to 0, because the used regex was buggy.
Add Ryan Kois as contributor.
Closes#20.
These options weren't used properly, because the s:line_* functions were
overwriting the sign texts. Now we initialize them only once at plugin
start.
Added Otto Modinos as contributor. Thanks for reporting.
Closes pull request #19.
I added 2 new options that are disabled by default. Sign updating can
now be triggered after 'updatetime' miliseconds without keypresses in
either normal or insert mode:
For enabling:
let g:signify_cursorhold_normal = 1
let g:signify_cursorhold_insert = 1
