Unfortunately, setenv only affects subprocesses, not the XEmacs process
itself. And since XEmacs is the process loading my DLL, Windows looks at
its PATH, not PATHs for subprocesses.
Andrew
On Tuesday, October 23, 2001, at 12:20 PM, Jerker Haglund wrote:
> I'm loading a DLL by name, but the DLL has to be in the XEmacs process'
> PATH for Windows to find it. The DLL comes from a plug-in we wrote, and
> we want to be able to load it just by putting in some lines into a
> user's .emacs file; rather than making them run a script that modifies
> their PATH first, and then runs XEmacs.
Try M-x setenv and M-x getenv.
In lisp it might be something like:
(setenv "PATH" (concat (getenv "PATH") "xxx;"))
If it's in your init file it should be inherited by all buffers, and to
any sub-processes.
/J. Haglund
-----------
Andrew Begel
Computer Science Division
UC Berkeley