"Stephen J. Turnbull" wrote:
>>>>> "Andrew" == Andrew Begel <abegel(a)eecs.berkeley.edu>
writes:
Andrew> Unfortunately, setenv only affects subprocesses, not the
Andrew> XEmacs process itself. And since XEmacs is the process
Andrew> loading my DLL, Windows looks at its PATH, not PATHs for
Andrew> subprocesses.
In general Emacs prefers to handle these things itself. Doesn't
`module-load-path' have the documented semantics under Windows?
yes, i agree, we should do it ourselves if possible to avoid unpredictable
library semantics.
We don't have a function that actually changes the environment. I
don't know why.
it's basically a matter of principle. we don't [didn't?] need it, so it
makes
for fewer surprises to always do things in process-environment and never the
actual environment.
e.g. in my mule ws i actually replaced all calls to getenv[] with egetenv[],
which checks process-environment, for encoding reasons.
I don't see why that would be dangerous, but I'm not
an expert on hairy process stuff. It's plausible that it just
got
omitted because it's a noop in an Emacs without dl capability.
I do know that Ben is rewriting the process stuff, see comments in
src/callproc.c, so you should coordinate with him on any addition.
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.