Can use sign_getdefined("...") (e.g. for "GitSignsAdded"), however there might be multiple options returned. The "length" (in quotes as nvim_buf_set_extmark seems to be okay with multibyte strings) of these signs might also not be 1 (which seems to be invalid), but they can be trimmed with string.sub(...).
No sanitizing of user input beyond checking that configuration values exist and that they are a string. Warnings will be output if the symbol ends up being too long or incorrect in some other way.
Defaults should remain the same as they are now.
Does not handle any other sign type than add, delete, or change (although gitsigns does offer more sign types).
A few notes when implementing this:
sign_getdefined("...")
(e.g. for"GitSignsAdded"
), however there might be multiple options returned. The "length" (in quotes asnvim_buf_set_extmark
seems to be okay with multibyte strings) of these signs might also not be1
(which seems to be invalid), but they can be trimmed withstring.sub(...)
.string
. Warnings will be output if the symbol ends up being too long or incorrect in some other way.add
,delete
, orchange
(althoughgitsigns
does offer more sign types).