unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: rost@mathematik.uni-bielefeld.de, emacs-devel@gnu.org,
	emacs-pretest-bug@gnu.org
Subject: Re: Emacs 21.3.50 grep.el/executable.el problems
Date: Mon, 16 Feb 2004 21:57:13 +0200	[thread overview]
Message-ID: <6408-Mon16Feb2004215712+0200-eliz@elta.co.il> (raw)
In-Reply-To: <jwvoerzdn01.fsf-monnier+emacs/devel@asado.iro.umontreal.ca> (message from Stefan Monnier on 16 Feb 2004 11:14:35 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: 16 Feb 2004 11:14:35 -0500
> 
> > I got the impression that the grep/executable problems don't get
> > fixed, because there should be perhaps a more extensive change.
> 
> My opinion is that the "extensive" change would be to rip out the recent
> change altogether.

I already did that, at Richard's request.

> What's the point of testing whether `find' is
> a unix-like find or not since if it isn't we have no good alternative
> anyway.  The only point I could see is to give a more meaningful error
> message for those few W32 folks who end up running some unrelated find.exe.
> But even then, I highly doubt it'll make any significant difference or is
> worth the trouble: the problem seem to be fairly infrequent and for those
> people who do end up posting on gnu.emacs.help, I expect they would post as
> well if the message said "you need to install a unix-like `find'" because
> they have no idea what the message is telling them and where to find
> a unix-like `find'.

In my experience, on a Windows system this problem is pretty frequent,
and when it happens, the error message that comes from the non-Posix
`find' is so cryptic that even occasional gurus get confused.

So IMHO a better error message from Emacs _is_ worth the trouble,
just not the kind of trouble that Jari got us into ;-)

  reply	other threads:[~2004-02-16 19:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 14:35 Emacs 21.3.50 grep.el/executable.el problems Markus Rost
2004-02-16 15:17 ` Ehud Karni
2004-02-16 16:14 ` Stefan Monnier
2004-02-16 19:57   ` Eli Zaretskii [this message]
2004-02-16 20:16     ` Stefan Monnier
2004-02-16 20:31       ` Jason Rumney
2004-02-16 21:10     ` Markus Rost
2004-02-17  6:34       ` Eli Zaretskii
2004-02-18  8:39       ` Richard Stallman
2004-02-18 20:55         ` Markus Rost
2004-02-17 17:27   ` Richard Stallman
2004-02-16 16:30 ` Kim F. Storm
2004-02-16 16:23   ` Markus Rost
  -- strict thread matches above, loose matches on Subject: below --
2004-02-13  6:32 Emacs 21.3.50 on cygwin bootstrap failed. (Jason Rumney) Steven Wu
2004-02-14 15:04 ` Emacs 21.3.50 grep.el/executable.el problems Ehud Karni
2004-02-15 11:43   ` Ehud Karni
2004-02-15 12:59     ` Piet van Oostrum
2004-02-15 13:20   ` Thien-Thi Nguyen

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=6408-Mon16Feb2004215712+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=rost@mathematik.uni-bielefeld.de \
    /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).