KConfig and $HOME

[Allen Winter]

On Friday 12 October 2007 2:37:46 am Thiago Macieira wrote:
> David Faure wrote:
> >On Thursday 11 October 2007, Thiago Macieira wrote:
> >> Ingo Klöcker wrote:
> >> >Does kconf_update support adding [$e] to config keys or do all
> >> >developers of KDE applications have to write ugly Perl scripts for
> >> >this?
> >>
> >> kconf_update is for updating user config files. Why would there be
> >> $HOME without [$e] on user config files (aside from manual tinkering)?
> >
> >Well, simply because kde3's writePathEntry didn't write it out? See your
> > ~/.kde/share/config/, it's full of values with $HOME without [$e].
> 
> Wow, I never knew this. Seems to me that we have to add this exception 
> then, because there are a few config files that are shared between KDE 3 
> and 4. Therefore, the file format must maintain backwards and forwards 
> compatibility.
> 
Thomas and PutHuhn,

We really need to be backwards compatible on this issue.
Please give KConfig the ability to read environment variables without the [$e].
Writing back out should use the [$e], however.

-Allen