From mboxrd@z Thu Jan 1 00:00:00 1970 Path: quimby.gnus.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.devel Subject: Re: Cygwin-mount.el (Was: Re: Using GDB in NTEMACS) Date: Sat, 23 Feb 2002 11:53:38 +0200 Message-ID: <2427-Sat23Feb2002115338+0200-eliz@is.elta.co.il> References: <3C6F2F5F.DCBC0805@is.elta.co.il> <5l4rketmyq.fsf@rum.cs.yale.edu> <3C71EC79.7EE4D14C@is.elta.co.il> <5leljhsfuf.fsf@rum.cs.yale.edu> <5lg03xqm84.fsf@rum.cs.yale.edu> <5lbselqjav.fsf@rum.cs.yale.edu> <3C73260B.C9111ECB@is.elta.co.il> <5l3czwqj3m.fsf@rum.cs.yale.edu> <3C73D10E.A08C2504@is.elta.co.il> <5lofijq13j.fsf@rum.cs.yale.edu> <87pu2zlppc.fsf@charter.net> <3C748F5B.6F50B5EF@is.elta.co.il> <874rkbxpar.fsf@charter.net> <3C74E05D.781AD1E0@is.elta.co.il> <5ly9hlo1ue.fsf@rum.cs.yale.edu> <6137-Fri22Feb2002210032+0200-eliz@is.elta.co.il> <200202221937.g1MJbNw31079@rum.cs.yale.edu> <8582-Fri22Feb2002224834+0200-eliz@is.elta.co.il> <4rk87dyk.fsf_-_@blue.sea.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: quimby2.netfonds.no X-Trace: quimby2.netfonds.no 1014458355 14572 195.204.10.66 (23 Feb 2002 09:59:15 GMT) X-Complaints-To: usenet@quimby2.netfonds.no NNTP-Posting-Date: 23 Feb 2002 09:59:15 GMT Cc: emacs-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby2.netfonds.no with esmtp (Exim 3.12 #1 (Debian)) id 16eYxX-0003mw-00 for ; Sat, 23 Feb 2002 10:59:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16eYvZ-0002Ft-00; Sat, 23 Feb 2002 04:57:13 -0500 Original-Received: from freya.inter.net.il ([192.114.186.14]) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16eYu3-0002DN-00 for ; Sat, 23 Feb 2002 04:55:39 -0500 Original-Received: from zaretsky (diup-220-205.inter.net.il [213.8.220.205]) by freya.inter.net.il (Mirapoint) with ESMTP id BFQ35232; Sat, 23 Feb 2002 11:55:30 +0200 (IST) Original-To: letters@hotpop.com X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <4rk87dyk.fsf_-_@blue.sea.net> (letters@hotpop.com) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: quimby.gnus.org gmane.emacs.devel:1452 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:1452 > 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