unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: monnier+gnu.emacs.help/news/@RUM.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: Using GDB in NTEMACS
Date: Fri, 22 Feb 2002 14:37:23 -0500	[thread overview]
Message-ID: <200202221937.g1MJbNw31079@rum.cs.yale.edu> (raw)
In-Reply-To: 6137-Fri22Feb2002210032+0200-eliz@is.elta.co.il

> Windows isn't Unix.  The current code will cause /cygdrive/d/foo to be
> interpreted as x:/cygdrive/d/foo (where x: is the drive letter of the

I'm not sure what current code you're talking about.  If you're talking
about the current Emacs code, then wether it's interpreted as
d:/cygdrive/d/foo or as x:/cygdrive/d/foo is irrelevant since the
filename is wrong anyway.
If you're talking about the current cygwin-mount.el code, then
/cygdrive/d/foo will be interpreted as d:/foo.

> But I cannot afford teaching you all those bits and pieces, pointing
> out all the subtle problems and explaining them, etc.  I don't have
> enough free time for that.  I gave a few examples on the news group,
> which should have been demonstrated some of the subtleties; if that
> wasn't enough, then I give up.

AFAIK you've given examples of ways in which recompiling a unix
program with cygwin can lead to unexpected problems (i.e. limitations
of the cygwin DLL), but I haven't seen any example where the use of
cygwin-mount.el introduces any problem (let along subtle ones).

I don't really care to know whether cygwin's Unix emulation is still
not perfect, all I care about is "why should Emacs not provide a way
to deal with /cygdrive/ paths".

> > Based on my understanding of cygwin's intent, there's no such hope
> > in the near future
> 
> I don't know on what you are basing this.  Did the Cygwin developers
> say they don't intend to fix this, ever?  Did anyone even ask them?

It's based on my understanding of their intent.  If their intent
is to provide a Unix API, then they pretty much have no choice.

> > >  Other similar projects made similar
> > > mistakes in the past.  The previous format of Cygwin names, //c/foo, was
> > > even nastier, so they changed that.  Obviously, Cygwin is on the right
> > > track, they just aren't there yet, IMO.  We should help them by sharing
> > > relevant experience and by requesting that misfeatures such as this one be
> > > solved better than they are now.  If we accept the current situation as
> > > satisfactory, we will get nowehere.
> > 
> > We have gotten nowhere since 1999 with the approach you're advocating.
> 
> We also have gotten nowhere in solving the problems of the famine in
> Africa or the war in Afghanistan.  Those are not our problems to solve.

It's not the same: those who suffer in our case are Emacs users.
Not just cygwin users.  So it is partly our problem.  We get questions
about it on gnu.emacs.help.
And on top of that, we can easily do something about it by including
something like cygwin-mount.el.


	Stefan


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  parent reply	other threads:[~2002-02-22 19:37 UTC|newest]

Thread overview: 16+ 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 [this message]
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
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
     [not found] <m37kp2qzhg.fsf@nyaumo.btinternet.com>
2002-02-27  4:00 ` Using GDB in NTEMACS Jon Cast

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=200202221937.g1MJbNw31079@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier+gnu.emacs.help/news/@RUM.cs.yale.edu \
    /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).