Open Aster89 opened 2 years ago
Technically the same holds for CSS files, which also have the same identical syntax for comments.
@andymass , what about the CSS file? Should I open another issue?
I have not decided yet if it is necessary to add this. Since all a user would need to do to get this (for any file type) would be to create a file in their configuration e.g., after/ftplugin/css.vim
:
call matchup#util#append_match_words('/\*:\*/')
On the other hand, if we add this by default to the plugin, is there any risk of adversely affecting anyone's configuration?
If it is so easy (obviously it works, thanks :smile:), then instead of adding this by default, why not writing this solution (a slight rewording of your latest comment) in the doc, e.g. under the FAQ Why does jumping not work for construct X in language Y??
Thanks, yeah, that is a good point. I took for granted that match_words and helper functions were documented somewhere but as you mention that is not really true. I will plan to add some FAQ/wiki mentions.
Is your feature request related to a problem? Please describe. I see that the opening
/*
and closing*/
of a JavaScript comment are not matched.Describe the solution you'd like The delimiters of inline C++ comments are matched, so I guess allowing the same in JavaScript is desirable (and easy-ish to implement?)
Describe alternatives you've considered Tbh, not jumping between beginning and end of a comment is not a urgent feature. Maybe a nice-to-have.
Additional context Not needed.