Open brendanator opened 6 years ago
I think this would be pretty straight-forward to implement. Do you have a suggestion for a default mapping for this? It should probably be a <Leader>
mapping, as I'm already trampling on spell checking with the current default mappings (see #6).
Ideally signs could be configurably grouped (e.g. all signs from a certain plugin) and those treated as a single section
I could probably implement this by allowing user-defined patterns that match against sign name
s. Ideally, this idea and the one in #8 should be implemented with the same solution.
Agreed that this should work with #8.
Don't know about default mappings, I personally would always configure this on so would suggest replacing ]s
etc. :smile:
Just had a thought that it might be nice to to use a contiguous region of signs as a text object too. Then could do something like yas
to yank the region. Can open an issue for this if you like it
Just had a thought that it might be nice to to use a contiguous region of signs as a text object too. Then could do something like yas to yank the region. Can open an issue for this if you like it
Please. I had considered this, but having an issue to keep track of would be helpful.
A text object might be a nice cherry-on-top, but jumping between contiguous regions is a must have for me. Since I use signs for diffs (vim-signify and vim-gitgutter) I often have large regions of signs. But I'd rather jump quickly to the places that have errors (e.g. as marked by vim-lsp).
If I have multiple lines in a row with a sign I would like to be able to jump to the next section of lines with a sign in it and skip over all the remaining ones in the section I am in
Ideally signs could be configurably grouped (e.g. all signs from a certain plugin) and those treated as a single section