[Github-comments] [geany/geany] Creating a user defined snippet config file produces a broken file by default (#2648)

elextr notifications at xxxxx
Sun Nov 8 07:07:43 UTC 2020


> How so?

You basically said it in the following sentence, the feature is for toggling blocks of code on/off during development without worrying about internal comments, its not for setting/unsetting comments for permanent use, which is why I made the note about users misunderstanding the feature and breaking it by setting the marker to something common in normal comments, like space.

Perhaps the feature should be renamed so it isn't the same as comment/uncomment in other editors, so users don't assume its the same without understanding it.

> make sure we only ever toggle on

Well, in this use that is all we need, so (without looking at how complex it is) we could add an extra parameter to the toggle comment code to limit it to on for uncommented lines only.  Or make a separate function, YMMV.

>  e.g. consider all lines uncommented no matter what.

Won't that double comment comments which is sure to cause issues full of commented comments comments. :grin:



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2648#issuecomment-723539469
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20201107/fd895198/attachment-0001.htm>


More information about the Github-comments mailing list