Skip to content

Conversation

@blueyed
Copy link
Contributor

@blueyed blueyed commented Jun 3, 2019

TODO: does not set/have the "sign" attribute (easily), only used with
AssertUniqueSigns, where it could be removed/replaced - maybe only for
the new method / if missing then?!

Fixes #83.

TODO: does not set/have the "sign" attribute (easily), only used with
AssertUniqueSigns, where it could be removed/replaced - maybe only for
the new method / if missing then?!

Fixes tomtom#83.
@blueyed
Copy link
Contributor Author

blueyed commented Jul 13, 2019

@tomtom any feedback?

@tomtom
Copy link
Owner

tomtom commented Jul 14, 2019

I currently have no recent version of vim available that already has the sign_*() functions, which is why I cannot test it etc.

I also wonder if qfs is still necessary with the new sign api since it originated in an effort to work around the limitations of the old api.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

s:ProcessSign does not handle new sign output

2 participants