<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Can you describe how does Emacs invoke OpenMCL, exactly?  IOW, with<br>
which Emacs command it is invoked, does the invocation go through a<br>
shell (and if so, which shell), etc.<br>
</blockquote></div><br></div><div class="gmail_extra">Problem closed.</div><div class="gmail_extra"><br></div><div class="gmail_extra">OpenMCL is started by comint-exec. The process-env variable was trashed by a spurious Slime configuration variable of mine.</div><div class="gmail_extra"><br></div><div class="gmail_extra">You can actually do :</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">(let ((process-environment (append "foo=bar" process-environment)))</div><div class="gmail_extra">  process-environment)</div><div class="gmail_extra">(102 111 111 61 98 97 114 "TEXINPUTS=.;c:/Home/.emacs.d/elpa/auctex-11.88/latex;" ...</div><div class="gmail_extra"><br></div><div class="gmail_extra">:-( I'm not sure if something can be done at the emacs level to check that this sensitive variable is not destroyed.</div><div class="gmail_extra"><br></div><div class="gmail_extra">For the record, it it useful to know that this 10106 winsock error relates to SYSTEMROOT environment variable being not defined.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Once the environment is properly passed to comint-exec, everything works as expected.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Fabrice</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div></div>