From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Cygwin-mount.el (Was: Re: Using GDB in NTEMACS)
Date: Sat, 23 Feb 2002 11:53:38 +0200 [thread overview]
Message-ID: <2427-Sat23Feb2002115338+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <4rk87dyk.fsf_-_@blue.sea.net> (letters@hotpop.com)
> From: letters@hotpop.com (Jari Aalto+mail.linux)
> Date: Sat, 23 Feb 2002 11:19:15 +0200
>
> If I understood correct, your premises are that:
>
> - If Emacs would include cygwin-mount.el, users expect to be able
> use FULL cygwin paths EVERYWHERE.
>
> I don't think that is a correct view. I don't see in a foreseeable
> future for anyone starting to use Cygwin style paths in their Lisp
> code or applications
You assume that any Cygwin-style file name comes from something a user
types. But that's not true: some file names are gotten from something
output by a program. This thread started (on gnu.emacs.help) because
someone could use GDB from GUD; that's one case where Emacs gets a
file name from a program. There are others: Dired, for example (if
the user wants to use the Cygwin port of `ls').
> Users want to MANAGE cygwin from Emacs. They do not want to "use
> cygwin paths" in their Emacs configuration. What I mean, is that users
> that have installed cygwin want to be able to use addresses like:
>
> C-x C-f /etc/passwd
>
> to configure their Apache, Inetd, Squid, Exim and
> other nifty stuff that can now be used natively under Windows.
You've just contradicted yourself, I think: to support /etc/passwd
like in the above example, we do need to handle Cygwin-style file
names everywhere in Emacs, because Emacs needs to know about the
Cygwin mount points.
> To require perfection before anything can be added to Emacs is
> a sad paths for Emacs.
I didn't require perfection. A good solution doesn't have to be
perfect, but it should be reasonably reliable, IMHO. If it hides
subtle bugs and misfeatures, it's broken.
> Cygwin is an Unix emulation, it should not understand DOS style
> paths at all.
As I explained earlier, there's no contradiction here. Cygwin
applications could support both styles.
> How the heck would a pure Unix application understand configuration
> file that would include dos paths?
By passing the file names unchanged into the Windows API.
> You can't expect to change 10 000 unix applications to support DOS
> paths.
Please re-read my messages in gnu.emacs.help: the changes are already
there in the sources, they just need to be used by the Cygwin build
(by simple modifications of the existing C preprocessor macros).
> Cygwin cannpt solve that in their libraries, because the application
> use the paths, not Cygwin.
That's true.
> Emacs is at least now pure windows application, so it understandas
> DOs paths. But it could be taught to understand cygwin paths and
> that change is small in the scope where cygwin paths are mainly
> used.
That's the crux of this argument: I don't think the change is small.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-23 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <u6phld6ea3r317@corp.supernews.com>
[not found] ` <3C6CDC0F.ECB82017@is.elta.co.il>
[not found] ` <m3n0y9xuf0.fsf@benny-ppc.crocodial.de>
[not found] ` <3C6F2F5F.DCBC0805@is.elta.co.il>
[not found] ` <5l4rketmyq.fsf@rum.cs.yale.edu>
[not found] ` <3C71EC79.7EE4D14C@is.elta.co.il>
[not found] ` <5leljhsfuf.fsf@rum.cs.yale.edu>
[not found] ` <m3k7t9z22l.fsf@nyaumo.btinternet.com>
[not found] ` <5lg03xqm84.fsf@rum.cs.yale.edu>
[not found] ` <m3bselz0b6.fsf@nyaumo.btinternet.com>
[not found] ` <5lbselqjav.fsf@rum.cs.yale.edu>
[not found] ` <3C73260B.C9111ECB@is.elta.co.il>
[not found] ` <5l3czwqj3m.fsf@rum.cs.yale.edu>
[not found] ` <3C73D10E.A08C2504@is.elta.co.il>
[not found] ` <5lofijq13j.fsf@rum.cs.yale.edu>
[not found] ` <87pu2zlppc.fsf@charter.net>
[not found] ` <3C748F5B.6F50B5EF@is.elta.co.il>
[not found] ` <874rkbxpar.fsf@charter.net>
[not found] ` <3C74E05D.781AD1E0@is.elta.co.il>
2002-02-22 17:36 ` Using GDB in NTEMACS Stefan Monnier <foo@acm.com>
2002-02-22 19:00 ` Eli Zaretskii
2002-02-22 19:30 ` Jon Cast
2002-02-22 19:55 ` Cygwin build (was: Using GDB in NTEMACS) Eli Zaretskii
2002-02-22 20:53 ` Using GDB in NTEMACS Jason Rumney
2002-02-24 1:32 ` Jason Rumney
2002-02-24 22:00 ` Jon Cast
2002-02-22 19:37 ` Stefan Monnier
2002-02-22 20:48 ` Eli Zaretskii
2002-02-23 9:19 ` Cygwin-mount.el (Was: Re: Using GDB in NTEMACS) Jari Aalto+mail.linux
2002-02-23 9:53 ` Eli Zaretskii [this message]
2002-02-22 21:01 ` Using GDB in NTEMACS Jason Rumney
2002-02-23 9:29 ` cygwin-mount.el (Was Re: Using GDB in NTEMACS) Jari Aalto+mail.emacs
2002-02-23 9:57 ` Eli Zaretskii
2002-02-26 10:06 ` Emacs for Cygwin (was: cygwin-mount.el, " Ehud Karni
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=2427-Sat23Feb2002115338+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--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 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).