From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: A few Windows build fixes
Date: Wed, 07 Sep 2011 08:50:37 -0400 [thread overview]
Message-ID: <jwvbouwsevl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1R1AWK-0008Cp-Rn@fencepost.gnu.org> (Eli Zaretskii's message of "Wed, 07 Sep 2011 01:17:56 -0400")
>> >> We'd want it to have zero impact to the users who don't use cygwin
>> >> (and may not even have it installed), of course.
>> > They will never see such file names.
>> That can be argued (all file names starting with "/" are potential
>> Cygwin names).
> I was talking about /cygdrive/x/ file names that should be translated
> to x:/ and vice versa. This must be on the C level, AFAIU.
For me, the convincing argument to add a "convert-external-file-name"
function to use on command-line args and such was specifically to be
able to handle *all* forms of Cygwin file names, including the ones that
are ambiguous (/home/foo was one motivating example, if I remember).
This was brought up in a feature-request for emacsclient arguments.
> The "mounted" file names, if we want or need to support them, will
> have to be looked up in the mount list taken from "mount -m".
FWIW, in that example, the mount point was "/some/where is mounted on /"
(and as it turns out the "mounted on /" is a case not handled by
cygwin-mount.el). So /home/foo really meant /some/where/home/foo, but
to figure that out, we'd first have to decide whether to interpret
/home/foo as a Cygwin name or as a native name.
> I don't see how the fact that Cygwin is or isn't installed is related
> to implementing the translation, except that "mount -m" will fail if
[...]
> Loading the Cygwin DLL into a native w32 process is impossible, so
> that's not an option.
I see, so indeed, Cygwin's availability is irrelevant since we won't use
the Cygwin DLL anyway.
>> I thought we still had problems delivering signals to them.
> You are right, we don't support sending Posix signals to Cygwin
> programs. But where is that a real problem? Emacs does know how to
> interrupt a subprocess, and the way it does that should work with
> Cygwin programs as well, albeit with less flexibility. After all,
> Cygwin programs are just specialized Windows applications.
It is a cause of problems for the SSL/TLS support (when we use
gnutls-cli rather than the gnutls DLL), for example.
Stefan
next prev parent reply other threads:[~2011-09-07 12:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 22:46 A few Windows build fixes Hannu Koivisto
2011-08-29 6:15 ` Eli Zaretskii
2011-08-29 8:18 ` Hannu Koivisto
2011-08-29 10:05 ` Eli Zaretskii
2011-08-29 12:03 ` Hannu Koivisto
2011-08-29 13:28 ` Eli Zaretskii
2011-08-29 15:55 ` Stefan Monnier
2011-08-29 16:11 ` Eli Zaretskii
2011-08-29 15:48 ` Stefan Monnier
2011-08-29 16:08 ` Eli Zaretskii
2011-08-29 19:48 ` Jan Djärv
2011-08-31 2:42 ` Vijay Lakshminarayanan
2011-08-31 6:11 ` Eli Zaretskii
2011-08-31 13:17 ` Stefan Monnier
2011-09-01 17:55 ` Vijay Lakshminarayanan
2011-09-02 0:14 ` Andy Moreton
2011-09-02 7:07 ` Eli Zaretskii
2011-09-02 11:43 ` Andy Moreton
2011-09-02 12:48 ` Stefan Monnier
2011-09-02 14:14 ` Eli Zaretskii
2011-09-02 14:18 ` Jason Rumney
2011-09-02 14:47 ` Stefan Monnier
2011-09-02 14:05 ` Eli Zaretskii
2011-09-02 14:48 ` Stefan Monnier
2011-09-02 15:48 ` Vijay Lakshminarayanan
2011-09-02 16:47 ` Eli Zaretskii
2011-09-06 2:49 ` Stefan Monnier
2011-09-06 4:33 ` Eli Zaretskii
2011-09-06 18:04 ` Stefan Monnier
2011-09-06 18:26 ` Eli Zaretskii
2011-09-07 3:29 ` Stefan Monnier
2011-09-07 5:17 ` Eli Zaretskii
2011-09-07 12:50 ` Stefan Monnier [this message]
2011-09-07 16:48 ` Eli Zaretskii
2011-09-08 8:33 ` Hannu Koivisto
2011-09-08 8:49 ` Eli Zaretskii
2011-09-08 9:06 ` Hannu Koivisto
2011-09-02 15:50 ` Vijay Lakshminarayanan
2011-09-02 2:48 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvbouwsevl.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=andrewjmoreton@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.