From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14541@debbugs.gnu.org
Subject: bug#14541: 24.3.50; `ediff-buffers' does not play well with recent Cygwin version
Date: Mon, 03 Jun 2013 18:40:38 +0300 [thread overview]
Message-ID: <83hahfxkw9.fsf@gnu.org> (raw)
In-Reply-To: <7d461150-fe55-4278-bb7a-22fc24811364@default>
> Date: Sun, 2 Jun 2013 21:12:40 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> I used to use an old (2007?) version of Cygwin. I just
> installed the latest Cygwin verion on Windows 7. I use the same setup
> for Emacs as previously (cygwin-mount.el, then setup-cygwin.el, both
> from Emacs Wiki).
>
> Previously, Cygwin handled MS DOS-style file names OK.
> But `ediff-buffers' passes such file names for its temporary files,
> and the latest version of Cygwin (on Windows 7 at least) does not,
> by default, handle such file names: it issues a warning, which means
> that Emacs raises an error and prints the Cygwin warning.
>
> This makes `ediff-buffers' unusable. There is a workaround: set env var
> CYGWIN to `nodosfilewarning'. I have added that to file setup-cygwin.el
> as a workaround.
May I again urge you to consider switching to MinGW ports instead? I
can point to those I use for years, which means they are reliable.
> But I wonder if `ediff-buffers' could perhaps prevent the error/warning
> anyway. I don't know whether it is really the 8-char DOS file-name
> format that Cygwin objects to, but I think so. Maybe just having it
> use full Windows (not DOS) file names would be a fix?
No. Cygwin wines about drive letters, not about the 8+3 aliases. So
using long file names will not help. You can verify that by invoking
Diff from the shell prompt.
We could perhaps push "CYGWIN=nodosfilewarning" into the environment
when Emacs launches child processes. However, as these URLs indicate:
http://stackoverflow.com/questions/9079982/cygwin-nodosfilewarning-doesnt-help-cygwin-warning
http://superuser.com/questions/370545/behaviour-of-cygwins-nodosfilewarning
this solution is not reliable if there's some other Cygwin process
running on the same system. So I think the only reliable solution is
to put the above into the System environment variables, so that
whatever the first Cygwin process is, it always sees it.
next prev parent reply other threads:[~2013-06-03 15:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 4:12 bug#14541: 24.3.50; `ediff-buffers' does not play well with recent Cygwin version Drew Adams
2013-06-03 15:40 ` Eli Zaretskii [this message]
[not found] <<7d461150-fe55-4278-bb7a-22fc24811364@default>
[not found] ` <<83hahfxkw9.fsf@gnu.org>
2013-06-03 16:21 ` Drew Adams
2013-06-03 16:37 ` Eli Zaretskii
2013-06-03 16:50 ` Achim Gratz
2013-06-03 20:15 ` Drew Adams
2013-06-03 20:23 ` Eli Zaretskii
2013-06-05 20:17 ` Achim Gratz
2013-06-05 23:55 ` Drew Adams
2013-06-06 19:07 ` Achim Gratz
2013-06-06 20:21 ` Eli Zaretskii
2022-02-13 9:26 ` Lars Ingebrigtsen
2013-06-06 20:42 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83hahfxkw9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14541@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).