Gentlemen, please see below.
From: ethersoft(a)gmail.com [mailto:ethersoft＠gmail.com] On
Behalf Of Vin Shelton
Sent: Thursday, January 26, 2006 8:55 AM
To: Per Mildner SICS Usenet; Robert Abad
Subject: Re: Latest 21.4.19 windows native setup kit uploaded
Thanks for following up.
On 1/26/06, Per Mildner SICS Usenet
> > - The binary directory for the user's XEmacs installation
> > to the system path.
> This is bad. You should not mess with the system global PATH.
Just as a point of etiquette, I'd recommend using slightly
less digital thinking. Design decisions may be "good (1)" or
from your point of view, but for most designers and users the
decisions likely fall somewhere on a spectrum of goodness
(even if you narrow the criteria to the one variable of
"goodness"). Rarely are things either just "good" or "bad"
and when you categorize them that way you run the risk of
alienating the people you are trying to convince (i.e. me).
> If XEmacs absolutely needs to have special folders on PATH
then it can
> set it in its own process (to be inherited by sub-processes).
I think understand where you're coming from. See
l and the follow-ups.
I believe Robert wants to run etags from a shell (not under
XEmacs) and he asked for the install kit to take care of
setting the path for him.
I was trying to run etags from an XEmacs shell (not a DOS shell). I
wasn't able to do this with 21.4.18 unless I [manually] edited my path
to include the etags directory. In 21.4.13, I did not need to do this.
Further investigation showed that 21.4.13 added a registry item called
Path to the registry which added the directory to the path for XEmacs
shells only (not the global system path). Version 21.4.18 does not add
this registry item.