Maybe it's a good idea also because it makes it more obvious which line was commented out.

Well with the current patch there are three types of lines, headings which are uncommented, comments which are "# " commented and settings that are "#" no space are commented¹.

Probably not to new users who are the ones fiddling with conf files, using # for a comment is "well known", but whats this #~ thing? And do I leave the ~ or what? Have had all those during various support interactions.

There is really no universally obvious solution, and if we add instructions in a comment at the top when we copy the file "Only remove the comment #~/# marker from lines you intend to change" on the off chance that users will read it, well either is as good/bad as the other.

its not clear from the G* docs for keyfile (can you see where the file format is described?) if space at the start of the setting line is ok or not, so not having a space on lines which are settings is best, so only the comment marker is removed. ↩

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

Footnotes