Allow configuring tree traversal start location #27
Labels
enhancement
New feature or request
Comments
JoosepAlviste
changed the title
JoosepAlviste
added a commit
that referenced
this issue
Nov 3, 2021
Make it possible to configure where the `commentstring` detection logic starts in the treesitter AST. The default is to start at the start of the cursor's line (first non-blank character). However, this is not 100% correct when commenting with motions. `update_commentstring` now accepts a location where to start the analysis so that when integrating with a commenting plugin, more granular control is possible. Additionally, a few useful helper functions are exported from `ts_context_commentstring.utils` which make it simpler to pass in a location. Resolves #27
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original issue / problem: numToStr/Comment.nvim#10 (comment)
Add a way to customize the location where the treesitter tree traversal is started (currently only on the first non-blank char on the cursor's line). This would make it possible to comment something like this in JSX when running
gciW:I think that it would make sense if
update_commentstringwould accept the position as an argument. If nothing passed in, then the cursor start of line, but if there is some location passed in, then we can use that one. For example, theComment.nvimintegration can usegetpos("'<")to get the visual selection start location instead of the cursor location. Or if there's no visual selection, then for the above example use the cursor location (or motion start location somehow?).The text was updated successfully, but these errors were encountered: