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: Tue, 06 Sep 2011 23:29:01 -0400 [thread overview]
Message-ID: <jwvty8prq5a.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83aaahjzmh.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 06 Sep 2011 21:26:46 +0300")
>> > Yes, we do: on the lowest possible level that Emacs handles file names
>> > before it passes them to system APIs. I pointed out the relevant
>> > function in w32.c where that happens. If you transform all file names
>> > there, every single feature of Emacs will work as expected by users.
>> You're talking about adding support for cygwin file names at the very
>> lowest level?
> I'm saying that this is the only way to have reliable support for
> Cygwin file names (as opposed to something that only "mostly" works).
>> 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). But the issue I was referring to is that we want the
Emacs executable to work even if Cygwin is not available, so either we
have to re-implement the Cygwin file-name translation (as is partly done
in cygwin-mount) or we have to dyn-load the Cygwin run-time
when available.
>> Also, once cygwin file names are supported, I think people will expect
>> more integration of (native) Emacs and cygwin, e.g. in subprocesses.
> What problems are there with Cygwin subprocesses? Emacs already
> recognizes Cygwin executables and adapts itself, at least to some
> extent (quoting of command-line arguments).
I thought we still had problems delivering signals to them.
If not, great.
Stefan
next prev parent reply other threads:[~2011-09-07 3:29 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 [this message]
2011-09-07 5:17 ` Eli Zaretskii
2011-09-07 12:50 ` Stefan Monnier
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=jwvty8prq5a.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.