all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>,
	cyd@mit.edu, emacs-devel@gnu.org
Subject: Re: Why should interactive search results raise errors?
Date: Thu, 04 May 2006 12:15:41 -0400	[thread overview]
Message-ID: <jwvejz93i1o.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1Fbedj-0002Au-U9@fencepost.gnu.org> (Richard Stallman's message of "Thu, 04 May 2006 10:17:11 -0400")

>     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'.

Clearly, the distinction between the two is only based on an expectation of
the context in which the function will be used.  So it's a heuristic and can
fail, but it on the flip side it also documents some of the intention behind
the code.
I think of it mostly as a way to clean up the debug-ignored-errors list.


        Stefan

  parent reply	other threads:[~2006-05-04 16:15 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
2006-05-04 14:20       ` Lennart Borgman
2006-05-04 15:34         ` Stuart D. Herring
2006-05-04 16:15       ` Stefan Monnier [this message]
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=jwvejz93i1o.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@mit.edu \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    /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.