KConfig and $HOME
Thomas Braxton
kde.braxton at gmail.com
Wed Oct 17 10:33:06 BST 2007
On 10/14/07, Oswald Buddenhagen <ossi at kde.org> wrote:
>
> > > > On Fri, Oct 12, 2007 at 11:50:30AM -0400, Allen Winter wrote:
> > > > > 1) support reading environment variables with or without the [$e]
> > > > > 2) support writing environment variables only with the [$e]
> > > > >
>
> > > On Sat, Oct 13, 2007 at 09:55:56AM -0500, Thomas Braxton wrote:
> > > > here's a patch that fixes readPathEntry,
> > > >
> > > scratch it. go with allen's suggestion.
> >
> > which suggestion?
> >
> the one quoted near the top of the mail? the one the entire mail was
> discussing? ;)
>
> > to read env variables with or without [$e]?
>
> > and if yes, shouldn't readPathList behave the same way?
> >
> of course it should. this is implied by induction. and 'readPath*Entry'
> pretty much implies it, too. ;)
Sorry about the delay, i just commited the fix. I also changed
readEntry<QString>/readEntry<QStringList> to behave like KDE3 and expand env
vars if [$e] was specified.
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071017/842b8f1c/attachment.htm>
More information about the kde-core-devel
mailing list