The reference to the desktop spec was what I was looking for, wonder why that
doesn't appear in the docs, it used to? Unfortunately it is not explicit about
leading spaces either, but [the
docodementation](https://gitlab.gnome.org/GNOME/glib/-/blob/main/glib/gkeyfile.c#L1277)
says leading
@techee pushed 1 commit.
766f756495e0704e7656773bdbf29f096ef45d16 fixup! Improve code commenting-out
global config files
--
View it on GitHub:
https://github.com/geany/geany/pull/3413/files/d43357f8cf8d08abda80a767c462c778e3e60683..766f756495e0704e7656773bdbf29f096ef45d16
You are receiving
> Kudos for the new source layout btw, makes for a very clean patch
You missed all the fun of the final "ctags sync" pull requests ;-).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3412#issuecomment-1445209091
You are receiving this because you are
> 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.
This is definitely a good reason to use just the simple `#` then.
>
Closed #1591 as completed via 2509e21526d36034f5251381a76555e7300fbfc0.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1591#event-8608208015
You are receiving this because you are subscribed to this thread.
Message ID:
Merged #3402 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3402#event-8608207954
You are receiving this because you are subscribed to this thread.
Message ID:
