unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
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 18:16:34 +0300	[thread overview]
Message-ID: <83eho325d9.fsf@gnu.org> (raw)
In-Reply-To: <jwvhat0m8oo.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Drew Adams <drew.adams@oracle.com>, 11999@debbugs.gnu.org
> Date: Sun, 22 Jul 2012 05:50:29 -0400
> 
> > 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?

Just what you wrote below.  (Thanks.)

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

What about an error condition that is neither of these two?  Or are
you saying that an error must be one of these two, and nothing else?

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

But it isn't a user error, either.  Perhaps we should find a better
name for that, as long as it isn't too late.





  parent reply	other threads:[~2012-07-22 15:16 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
2012-07-22 14:34             ` Drew Adams
2012-07-22 15:16             ` Eli Zaretskii [this message]
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=83eho325d9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=11999@debbugs.gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).