-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCS signs overlayed with generic marks #71
Comments
Alternatively, it might be good to define/configure the order of signs,
so that the |vcs| related ones would be placed after the more generic
marks?!
Sign definitions have a level field. For g:quickfixsigns_class_marks
this is 4, for g:quickfixsigns_class_qfl it is 7. If you want qfl to
take precedence, set it to 3 -- should work. Currently there is no way
to configure just the level field easily.
|
What I've meant is to merge them, which in this case would use the background from the For this to work there would need to be intermediate texthl classes for the signs, e.g. It's not trivial, but hopefully you get what I mean at least?! :) |
I think merging is a bad idea. Signs are a pain anyway. I think you should use the |
With the following signs for the same line, it would be nice to get the background of the "VCS ADD" sign:
Currently only the
.
sign is visible, which has no background and therefore no indication about this line being changed (with regard to thevcsdiff
module).To indicate that this line was added, it might be nice to have a sign there that merges
QFS_Mark_.
andQFS_VCS_CHANGE
maybe, i.e. using thetext
fromQFS_Mark_.
with thetexthl
fromQFS_VCS_CHANGE
?!Alternatively, it might be good to define/configure the order of signs, so that the
vcs
related ones would be placed after the more generic marks?!The text was updated successfully, but these errors were encountered: