You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Expected: fall back to block comments when line comments are unavailable
There's a twist, though: in some editors (like Sublime), the block comment behavior is subtly different when invoked as a fallback like this. When there's no selection, the entire line is wrapped in a block comment (the normal behavior, and what you get if you invoke block comment explicitly, is to insert an empty block comment at the cursor position).
The text was updated successfully, but these errors were encountered:
This is what i was planning to implement next, but wasn't sure if it should just make a block comment over the selection, or over all the lines in the selection. Maybe this second approach might work better on HTML, where commenting a block over several lines that don't include the complete lines is not usual.
In any case, it should be easy enough, by adding an additional parameter to block-comment with the positions for the prefix and suffix in the case of a block-comment.
Result: nothing happens
Expected: fall back to block comments when line comments are unavailable
There's a twist, though: in some editors (like Sublime), the block comment behavior is subtly different when invoked as a fallback like this. When there's no selection, the entire line is wrapped in a block comment (the normal behavior, and what you get if you invoke block comment explicitly, is to insert an empty block comment at the cursor position).
The text was updated successfully, but these errors were encountered: