unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11999@debbugs.gnu.org
Subject: bug#11999: 24.1.50; New Info file suffix ".info" breaks `Info-find-node-2'
Date: Sun, 22 Jul 2012 05:50:29 -0400	[thread overview]
Message-ID: <jwvhat0m8oo.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83sjcl7b5w.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Jul 2012 11:47:55 +0300")

> The doc string IMO does not tell enough, and there's no other
> documentation about user-error, neither in the ELisp manual nor in
> NEWS (which only mentions its existence).

Can you be specific about what additional info you need?

> Stefan, could you perhaps provide some insight?  What is a "pilot
> error" in this context,

A error of the user rather than of the author of the code.

> and how should Lisp programs use this new facility to (supposedly)
> provide better diagnostics and/or better error handling?

user-error is just a standard "debug-ignored-error".  So instead of
using error plus adding the text of the error to debug-ignored-errors,
you can just user user-error.

If Drew gets a user-error that drops him in the debugger, it's because
he removed` user-error' from debug-ignored-errors.

>> An index lookup that finds no hit is NOT "expected to be the result of an
>> incorrect manipulation on the part of the user, rather than the result of an
>> actual problem." 

By "actual problem", I meant "a bug in the code", i.e. a problem that
can be fixed by correcting the code.


        Stefan





  parent reply	other threads:[~2012-07-22  9:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 16:13 bug#11999: 24.1.50; New Info file suffix ".info" breaks `Info-find-node-2' Drew Adams
2012-07-20 18:30 ` Andreas Schwab
2012-07-20 18:45   ` Drew Adams
2012-07-20 19:19     ` Andreas Schwab
2012-07-20 20:03       ` Drew Adams
2012-07-20 20:08         ` Andreas Schwab
2012-07-20 20:09           ` Drew Adams
2012-07-20 20:11             ` Andreas Schwab
2012-07-20 20:47         ` Eli Zaretskii
2012-07-20 20:43     ` Eli Zaretskii
2012-07-20 21:08       ` Drew Adams
2012-07-21  8:47         ` Eli Zaretskii
2012-07-21 13:58           ` Drew Adams
2012-07-22  9:50           ` Stefan Monnier [this message]
2012-07-22 14:34             ` Drew Adams
2012-07-22 15:16             ` Eli Zaretskii
2012-07-23  8:53               ` Stefan Monnier
2012-07-23 13:54                 ` Drew Adams
2012-07-23 23:28                   ` Stefan Monnier
2012-07-24  1:30                     ` Drew Adams
2012-07-24  9:02                       ` Stefan Monnier
2012-07-24 16:38                 ` Eli Zaretskii
2012-07-24 21:53                   ` Stefan Monnier
2012-07-25 16:06                     ` Eli Zaretskii
2012-07-25 23:53                       ` Stefan Monnier
2012-07-26  3:06                         ` Eli Zaretskii
2012-07-26 23:18                           ` Stefan Monnier
2012-07-27  6:49                             ` Eli Zaretskii
2012-07-28 21:36                               ` Stefan Monnier
2012-07-29  2:50                                 ` Eli Zaretskii
2012-07-30  9:30                                   ` Stefan Monnier
2012-07-30 13:35                                     ` Eli Zaretskii
2012-07-29  6:30                                 ` Juri Linkov

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=jwvhat0m8oo.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=11999@debbugs.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).