5:03 p.m.
Gentlemen, please see below.
-----Original Message-----
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
Cc: xemacs-beta
Subject: Re: Latest 21.4.19 windows native setup kit uploaded
Dear Per,
Thanks for following up.
On 1/26/06, Per Mildner SICS Usenet
<PerMildnerSICSUsenet(a)hotmail.com> wrote:
> > - The binary directory for the user's XEmacs installation
gets added
> > 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
"bad (0)"
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
http://list-archive.xemacs.org/xemacs-beta/200601/msg00262.htm
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.
Regards,
Vin
7 p.m.
New subject: Latest 21.4.19 windows native setup kit uploaded
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.
There should not even be necessary to have any paths in the registry,
xemacs.exe should figure out where it is located and use that to find the
location of any related files and folders. It could then set its environment
variable PATH so that any sub-shells/sub-processes can find the xemacs tools
from their inherited value of PATH.
1:12 a.m.
New subject: Latest 21.4.19 windows native setup kit uploaded
On 1/26/06, Per Mildner SICS Usenet <PerMildnerSICSUsenet(a)hotmail.com> wrote:
> 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.
There should not even be necessary to have any paths in the registry,
xemacs.exe should figure out where it is located and use that to find the
location of any related files and folders. It could then set its environment
variable PATH so that any sub-shells/sub-processes can find the xemacs tools
from their inherited value of PATH.
Robert,
Just add this bit of elisp to your .emacs or (.xemacs/init.el) file:
(setenv "PATH"
(concat (getenv "PATH")
(car (last exec-path))))
This should make sure that the directory containing etags gets added
to your shell's path.
Basically, I agree with Per and I'd rather not add an XEmacs directory
to the system path if I can avoid it, so I will be removing that
feature from the setup kit.
- Vin
PS. As you can see above, the XEmacs startup code does add the
necesary directory to exec-path, but the PATH environment variable
does not get set to the value of exec-path, so sub-processes do not
inherit that value.
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver
1:14 p.m.
New subject: Multiple issues with InnoSetup XEmacs
Today I downloaded and installed the final 21.4.19 InnoSetup version of
XEmacs but it still uses the wrong efs-ftp-program-name C:\WINNT\....
Interestingly, if I start xemacs with -no-init-file and do
update-installed-packages then efs-ftp-program-name has the value "ftp" but
I pretty sure that my init files does not set efs-ftp-program-name.
In any case, with or without -no-init-file i get an error "liece is not a
valid package",
If I start with -no-init-file, does not select a package download location
and selects "Update Installed Packages" from the Tools menu, I get the same
error with the following in *Message-Log*:
Loading package-get...
Loading package-get...done
Got 123 package-get database entries
Updated package database
Loading efs-cu...
Loading efs-cu...done
Invalid argument: "liece is not a valid package"
(I sent this already but forgot the xemacs-beta list)
Regards,
6644
days inactive
6658
days old
3 comments
3 participants
participants (3)
-
Per Mildner SICS Usenet -
Robert Abad -
Vin Shelton