all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, cyd@mit.edu
Subject: Re: Why should interactive search results raise errors?
Date: Thu, 04 May 2006 10:17:11 -0400	[thread overview]
Message-ID: <E1Fbedj-0002Au-U9@fencepost.gnu.org> (raw)
In-Reply-To: <4458DF5F.6010309@student.lu.se> (message from Lennart Borgman on Wed, 03 May 2006 18:50:39 +0200)

    I still believe that interactive search commands should not raise 
    errors. However I think adding these commands now to 
    debug-ingnored-errors is the better solution now. Could we please do 
    that now?

I see no reason to change this.  Lots of commands signal errors when
they can't do what they are asked to do; why shouldn't these?

    I think the better answer is to create a new error class called `user-error'
    which would be then added to debug-ignored-errors.  Then we can replace most
    elements of debug-ignored-errors by changing the signalling code so as to
    signal a `user-error' rather than an `error'.

That is not necessarily a bad idea, but I am not sure whether it is
really possible to distinguish "user errors" from other errors at the
level of calls to `signal'.

`debug-ignored-errors' does make an attempt to distinguish which
errors are _probably_ user errors, but it cannot really know,
and sometimes this criterion gets the wrong answer.

  reply	other threads:[~2006-05-04 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 16:26 Why should interactive search results raise errors? Lennart Borgman
2006-05-03 16:34 ` Chong Yidong
2006-05-03 16:50   ` Lennart Borgman
2006-05-04 14:17     ` Richard Stallman [this message]
2006-05-04 14:20       ` Lennart Borgman
2006-05-04 15:34         ` Stuart D. Herring
2006-05-04 16:15       ` Stefan Monnier
2006-05-03 17:29 ` Stefan Monnier
2006-05-03 19:58   ` Lennart Borgman
2006-05-04  8:34 ` Kim F. Storm
  -- strict thread matches above, loose matches on Subject: below --
2006-05-04  9:21 LENNART BORGMAN
2006-05-04  9:58 ` Miles Bader

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Fbedj-0002Au-U9@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=cyd@mit.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.