unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: RE: No such program, egrep error in Customize
Date: Wed, 26 Dec 2007 12:02:15 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICAEEEECAA.drew.adams@oracle.com> (raw)
In-Reply-To: <uzlvxgrvw.fsf@gnu.org>

> > Still, the error message is perhaps a bit strange. ispell is
> > apparently used for completion of strings, but if ispell is
> > not installed, then that's not TRT.
>
> No, ispell (the program) is not used for completion.  Instead, you
> will see that ispell.el invokes the program that is the value of
> ispell-grep-command directly, as this backtrace you posted clearly
> shows:
>
>   ispell-call-process("egrep" nil t nil "-i" "^blu.*$" "/usr/dict/words")
>
> (`ispell-call-process' is a simple wrapper for call-process-region, it
> does NOT invoke ispell the program.)

Thanks for the clarification. Let me rephrase it then. The code that calls
ispell-call-process with "egrep", or some higher-level code, should perhaps
provide a better error message for a Customize user.

And see my other mail. It is better for such a failure to find egrep not to
raise an error and instead call some default text-completion function.

There are perhaps other, and better ways to handle this, but I don't think
the current approach is very user-friendly, in any case. Especially for a
Customize user. At the limit, it is better to punt and say completion is not
available than to send the user googling to figure out what egrep and
ispell-call-process might be all about.





  reply	other threads:[~2007-12-26 20:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 18:32 No such program, egrep error in Customize Drew Adams
2007-12-26 18:54 ` Drew Adams
2007-12-26 19:18   ` Andreas Schwab
2007-12-26 19:45     ` Drew Adams
2007-12-26 19:50     ` Eli Zaretskii
2007-12-26 19:18   ` Drew Adams
2007-12-26 19:47     ` Eli Zaretskii
2007-12-26 20:02       ` Drew Adams [this message]
2007-12-26 19:41 ` Eli Zaretskii
2007-12-26 19:53   ` Drew Adams
2007-12-29 12:42   ` Eli Zaretskii

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=DNEMKBNJBGPAOPIJOOICAEEEECAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=eliz@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).