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
When I start a new JSDoc comment, e.g., I'm used to having to type only the following in most code editors: /**<space><ret>.
The resulting comment structure then becomes this, where | is the caret:
/** * | */
I would love for this to be possible in Helix as well. And for it also to keep adding new *'s as I press enter, or reach the wrap limit (or at least when I run :reflow). (This was happening when I was typing the code for these comments in the GitHub issue text area, even.)
Would also love this for the regular /*<space><ret>, to result in:
/* | */
or maybe
/* * | */
Maybe even typing just /**<space> would result in /** | */? And similar for /*<space>?
It would make writing comments a lot smoother in my opinion. I'd be very content with :reflow learning this capability, at least.
Let me know what you think, please! And thank you for your time!
The text was updated successfully, but these errors were encountered:
When I start a new JSDoc comment, e.g., I'm used to having to type only the following in most code editors:
/**<space><ret>
.The resulting comment structure then becomes this, where
|
is the caret:I would love for this to be possible in Helix as well. And for it also to keep adding new
*
's as I press enter, or reach the wrap limit (or at least when I run:reflow
). (This was happening when I was typing the code for these comments in the GitHub issue text area, even.)Would also love this for the regular
/*<space><ret>
, to result in:or maybe
Maybe even typing just
/**<space>
would result in/** | */
? And similar for/*<space>
?It would make writing comments a lot smoother in my opinion. I'd be very content with
:reflow
learning this capability, at least.Let me know what you think, please! And thank you for your time!
The text was updated successfully, but these errors were encountered: