[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: some emacs-21.1.1 problems

From: Jason Rumney
Subject: Re: some emacs-21.1.1 problems
Date: Thu, 22 Nov 2001 06:36:56 +1200

>J.Rumney wrote: 
>>>3. With mailcrypt-3.5.6, gnupg-1.0.6: when decrypting a buffer:
>>>"start-process: Removing old name: no such file or directory,
>>>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?
>Cygwin interprets filepaths

You cannot rely on how Cygwin interprets paths for the interaction
between Emacs and external applications.

Which is why I said...

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

>Cygwin by default mounts its installation directory, in my case
>"c:\Tools\cygwin" to "/". So "/tmp" always refers to the "tmp"
>directory under cygwin's install directory.

No, it doesn't. It only refers to that directory if the application
that references it is a Cygwin app. To other apps, "/tmp"
is a directory at the root of the current drive.

>Unfortunately, I could not use "c:/tmp", since cygwin
>does translate
>this value into "/cygdrive/c/tmp". So I chose this
>latter value
> also for the ELisp variables.

No!!! To any Windows program (Emacs included),
refers to the file "X:\cygdrive\c\tmp", where X is the current

If your Cygwin applications do not understand normal Windows paths,
they are broken. I suggest you throw them out and get some new tools.

>I agree with your analysis. One tool creates the file, another one
>wants to delete it, but doesn't find it. Some of the processes that
>are spawned in the background do understand Unix-like file names,
>others, as well as the ELisp code, don't. Maybe, if the "d:" was not
>prepended (see above), everything would work fine.

The d: MUST be prepended, otherwise it is ambiguous
whether you
are refering to c:\tmp or d:\tmp.

>I would like to compile emacs under cygwin in order to get rid of
>these pathname problems (Xemacs/cygwin does work rather smoothly), but
>didn't succeed so far.

Emacs does not compile under Cygwin.

If you do not wish to use Windows, I can suggest a very good
replacement that is also Free Software; GNU/Linux.

I do not recommend immersing yourself in Cygwin, pretending
that Windows does not exist, and cursing every app that does
not conform to the Cygwin way.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]