15 Mar
2011
15 Mar
'11
11:19 p.m.
Yes, startkde tries to check this variable. If not already explictly set, startkde
presumes to set the variable to $HOME/.kde.
That will trash the user's KDE4 profile even if the OS does not explictly define
$KDEHOME because $HOME/.kde is the default profile location for KDE4.
Further, the default in startkde conflicts with kdelibs/kdecore/kstandardirs.cpp.
Bug report 459 filed.
Darrell
--- On Tue, 3/15/11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
From: Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>
Subject: Re: [trinity-devel] $KDEHOME
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Tuesday, March 15, 2011, 5:55 PM
On Tue, Mar 15, 2011 at 4:34 PM,
Darrell
Anderson
<humanreadable(a)yahoo.com>
wrote:
> I don't read c++ very well. Seems to me
that if
$KDEHOME is not
> explicitly defined then Trinity defaults to
$HOME/.kde3. Yet the
> comments in kstandardirs.h declare $HOME/.kde
as
the default.
>
<snip>
The startkde script primarily determines $KDEHOME
IIRC. If there is a
secondary default in the code, then it should be set to
$HOME/.trinity.
If this is not the case, then a bug report should be
filed.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting