From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: A few Windows build fixes
Date: Tue, 06 Sep 2011 00:33:45 -0400 [thread overview]
Message-ID: <E1R0nM1-0001YW-KF@fencepost.gnu.org> (raw)
In-Reply-To: <jwvhb4qxu6o.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 05 Sep 2011 22:49:52 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
> Date: Mon, 05 Sep 2011 22:49:52 -0400
>
> >> > It doesn't matter who and how runs "mount -m". The results of that
> >> > should be used on the C level. Otherwise, the result will be
> >> I don't think so: we only want to convert cygwin file names when they
> >> "enter" Emacs and everything else (e.g. all primitives that access
> >> files) should not know about them.
> > You cannot possibly hope to plug all the holes this way. A file name
> > can "enter" Emacs in any number of ways, including as a substring of
> > some string or buffer. Trying to catch all those loopholes is never
> > going to work reliably.
>
> We have no chance to plug all hole reliably anyway.
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.
> The closest to
> "handle it everywhere" already exists, it's called cygwin-mount.el.
cygwin-mount is part of the solution, but it isn't all of it. If we
want a reliable solution, that is (which IMO is what users expect).
> Instead we want something that's less intrusive, even though it will
> miss a few more cases (but by being less intrusive it can work
> better in the cases where it does work).
Something that happens in one or 2 functions cannot be intrusive.
next prev parent reply other threads:[~2011-09-06 4:33 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 [this message]
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
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
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=E1R0nM1-0001YW-KF@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).