How to learn about all those configuration file values?

Stephen Dowdy sdowdy at
Sun Apr 7 21:54:45 BST 2013

Kevin Krammer wrote, On 04/07/2013 03:34 AM:

> A lot of application config are nowadays described by a meta config file, file extension being .kfcg


> They are used to describe all possible values, their types and defaults and are used to generate config access code instead of manually writing it (manually written config access code is prone to typos in setting names).



Heh, Irony Oops! You typo'd the file extension (.kfcg) should be
.kcfg (that sequence of letters is always a tough one)

$ kde4-config --path kcfg

While i'd just sort of discovered these in looking in more depth in
trying to determine where these might be found, i never even noticed
that there was a 'kcfg' path, and hadn't looked in detail...

> But as a side affect the also provide a kind of documentation of the application's configuration capabilities.

Yep, cool.. (where's 'kxmleditor' when you need it? anybody know of
a good replacement XML visualization tool? )

So, i presume these files are simply compile-time reference material
when placed in that directory, and are not runtime referenced by the
application. (i.e. it's going to be up to the "distro" maintainer to
ensure they get put there so the average user can reference them, to
see what key values may have been default-overridden at compile-time
in the packaging.)

I see:
as the reference.

> kwrited is a system facility integration plugin. It provides the necessary interfaces for Unix local system instant messaging tools like talk or write.
> Those are not in common use anymore, especially not on single user systems, and thus not loading that plugin by default makes a low hanging fruit for saving some resources.

Yeah, i used 'talk/write' a lot back in the mid 1980's, but haven't
used it except a couple times in the past decade.

This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list