Re: [Evolution] Documenting DEBUG variables

[Matthew Barnes <mbarnes redhat com>]

On Wed, 2011-08-24 at 19:38 +0200, Andre Klapper wrote:
> If any further variables that can be set by users come to anybody's
> mind, please mention them (plus their potential values) so I can list
> them.
>
> A quick grep for _DEBUG shows:
> * evolution
...
>   * G_ENABLE_DEBUG
...
> * evolution-data-server
...
>   * G_ENABLE_DEBUG
...

Weird.  I'm not sure where you got G_ENABLE_DEBUG from, as that doesn't
show up in my grep.  G_ENABLE_DEBUG is internal to GLib.  Means its been
built with debugging features enabled, such as reference count tracking.
It's of no use for Evolution users.

In fact other than ALARMS_DEBUG, I'd just strike all the other Evolution
variables.  ALARMS_DEBUG is for the alarm daemon, which can sometimes be
useful for missed reminders.  But it's the backend variables in E-D-S
and the extension packages that show raw network protocol chatter, etc.

In E-D-S there's also GOOGLE_BACKEND_DEBUG for Google Contacts.