[Geany-devel] GLib 2.32 and debug messages

[Lex Trotman]

[...]
> ?  These environment variables are documented so why is it worst than a
> configuration file somewhere?

Couple (or 3) reasons:

1. with most desktops it seems running geany from the menu or icon
won't set environment variables because no shell runs to read .bashrc
or whatever setup file

2. as far as I can find its only documented in the Glib documentation,
not somewhere even an experienced *user* is likely to look

3. As a general comment, how often have you taken ages to find that
you had to set path to make something work because no installer can
set it for you?

All should be command line options IM(not so)HO so they are explicit
and in user documentation.  The config file is just a way of saving
you having to type too much , just like gcc @file, file can be
distributed to set things.

Cheers
Lex

>
>>> The problem is that it breaks our `-v` option, since we simply turns on
>>> outputting INFO-level messages.  So, we need a fix or a workaround,
>>> something.  I see 2 solutions:
>>>
>>> 1) simply `g_setenv("G_MESSAGES_DEBUG", "all", TRUE)` when given `-v`
>>> (e.g. around main.c:131, `if (app->debug_mode) g_setenv(...`)
>>
>> Maybe do this for pending release ...
>
> I did this.

Okey dokey.

>
>>> 2) output everything ourselves in `handler_log()` (log.c:115) rather
>>> than calling GLib's default handler.
>>>
>>
>> ... and this later for "proper" fix that allows us to tailor it as we
>> need, unless this is very simple too.
>
> Well.  It's easy to output something.  It's harder to output something
> as useful as what the GLib handler can output, like including prgname,
> pid & co, an doing so to the proper stream.  Not really hard, but not
> trivial either.
>

Well, if we have to re-invent the wheel then don't bother.

>>> [...]