Does that include saving paths the user might have entered?
I think the easiest spot for errors to crop up would be when you store a
path in a config file and don't bother to check if it begins with $HOME
and convert it back to a relative reference.
On 12-12-01 11:33 AM, PCMan wrote:
> If you're talking about the core components, the answer is none.
> We always get home dir on the fly and avoid hard-coded paths.
>
> On Sat, Dec 1, 2012 at 9:40 PM, <u-lxdel0tf@...> wrote:
>> Hello,
>>
>> I am curious how much the setting management in LXDE is dependent
>> on the $HOME path being "constant".
>>
>> >From the experience I know that certain applications are obstinate
>> to store absolute paths to objects to be found under $HOME - which of
>> course breaks if the home changes and moves all such objects to the new
>> corresponding paths.
>>
>> Wonder whether or how much the different parts of LXDE are subject to such
>> a design mistake?
>>
>> Regards,
>> Rune
>>
>>
>> ------------------------------------------------------------------------------
>> Keep yourself connected to Go Parallel:
>> INSIGHTS What's next for parallel hardware, programming and related areas?
>> Interviews and blogs by thought leaders keep you ahead of the curve.
>> http://goparallel.sourceforge.net
>> _______________________________________________
>> Lxde-list mailing list
>> Lxde-list@...
>> https://lists.sourceforge.net/lists/listinfo/lxde-list
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
>

Thanks,
On Sun, Dec 02, 2012 at 12:33:41AM +0800, PCMan wrote:
> If you're talking about the core components, the answer is none.
> We always get home dir on the fly and avoid hard-coded paths.
Sounds good!
Regards,
Rune

If you're talking about the core components, the answer is none.
We always get home dir on the fly and avoid hard-coded paths.
On Sat, Dec 1, 2012 at 9:40 PM, <u-lxdel0tf@...> wrote:
> Hello,
>
> I am curious how much the setting management in LXDE is dependent
> on the $HOME path being "constant".
>
> >From the experience I know that certain applications are obstinate
> to store absolute paths to objects to be found under $HOME - which of
> course breaks if the home changes and moves all such objects to the new
> corresponding paths.
>
> Wonder whether or how much the different parts of LXDE are subject to such
> a design mistake?
>
> Regards,
> Rune
>
>
> ------------------------------------------------------------------------------
> Keep yourself connected to Go Parallel:
> INSIGHTS What's next for parallel hardware, programming and related areas?
> Interviews and blogs by thought leaders keep you ahead of the curve.
> http://goparallel.sourceforge.net
> _______________________________________________
> Lxde-list mailing list
> Lxde-list@...
> https://lists.sourceforge.net/lists/listinfo/lxde-list

Hello,
I am curious how much the setting management in LXDE is dependent
on the $HOME path being "constant".
>From the experience I know that certain applications are obstinate
to store absolute paths to objects to be found under $HOME - which of
course breaks if the home changes and moves all such objects to the new
corresponding paths.
Wonder whether or how much the different parts of LXDE are subject to such
a design mistake?
Regards,
Rune