Latest 21.4.19 windows native setup kit uploaded

[Vin Shelton]

On 1/26/06, Per Mildner SICS Usenet <PerMildnerSICSUsenet at 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