Re: some emacs-21.1.1 problems

[Jason Rumney]

>3. With mailcrypt-3.5.6, gnupg-1.0.6: when decrypting a buffer:
>"start-process: Removing old name: no such file or directory,
>d:/tmp/mailcrypt-gpg-stderr-764AJM".
>
>E.Karni wrote: 
>> So the directory "d:\tmp" does exist on that system, yes?
>
>Yes, I have c:\tmp, d:\tmp, c:\Tools\cygwin\tmp. 

So how do you know which of the above "/tmp" is refering to
at any one point in time?

>Furthermore, 
>
># echo $TMP
>/tmp
># echo $TMPDIR
>/tmp

This is a dangerous way to set TMP and TMPDIR on Windows. Please specify a drive
letter.

>I also tried out several versions of mentioning tmp directories in
>mailcrypt.el, e.g.
>
>(defvar mc-temp-directory "d:\\tmp"
>  "*Default temp directory to be used by Mailcrypt.")

You should use setq to set variables, not defvar.
defvar is for defining variables, and will not override existing values.
>Note that temporary-file-directory has the value,

>Neither did work. But the error message cited above ("start-process"
>...) was always adapted to the new tmp path.

Then there is a bug in mailcrypt. Perhaps it relies on TMP (or
TMPDIR or TEMP) being the same as mc-temp-directory?

>> From the error message, it sounds like the problem happens in the
>> delete-file primitive, but I cannot figure out how is start-process
>> related to that.

I think mailcrypt creates a temporary file, then deletes it
when finished. Maybe the temporary file is created by gpg/pgp,
so both need to be looking at the same temporary directory.
(From backtrace)

(shell-file-name "/bin/sh")

This is probably the same version of bash that you are having
problems with. Is it possible that this version of bash is
responsible for ALL these problems? Could you try setting
any environment or elisp variables that point to bash or /bin/sh
back to %emacs_dir%\bin\cmdproxy.exe.