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 writing comments such as documentation comments, it is pretty annoying that the comment token (//! or /// in Rust for example) isn't prepended to the next line when ENTER is hit. This can mess up the flow of writing comments as you have to manually type the comment token every time. It would be nice if Helix used the comment token (the one specified by the comment-token field under [[language]] in languages.toml) and prepend it to the next line, with a space, when ENTER is hit.
There would of course be some questions that could arise with this feature. In Rust, for example, there are multiple kinds of comment tokens that start with //. How would Helix handle this? One suggestion of mine would be to somehow check if there is another character after the // prefix and append that to some "buffer" caching the token prefix. This would require some discussion though I believe.
The text was updated successfully, but these errors were encountered:
When writing comments such as documentation comments, it is pretty annoying that the comment token (
//!
or///
in Rust for example) isn't prepended to the next line when ENTER is hit. This can mess up the flow of writing comments as you have to manually type the comment token every time. It would be nice if Helix used the comment token (the one specified by thecomment-token
field under[[language]]
inlanguages.toml
) and prepend it to the next line, with a space, when ENTER is hit.There would of course be some questions that could arise with this feature. In Rust, for example, there are multiple kinds of comment tokens that start with
//
. How would Helix handle this? One suggestion of mine would be to somehow check if there is another character after the//
prefix and append that to some "buffer" caching the token prefix. This would require some discussion though I believe.The text was updated successfully, but these errors were encountered: