From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>,
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: Sat, 21 Jul 2012 11:47:55 +0300 [thread overview]
Message-ID: <83sjcl7b5w.fsf@gnu.org> (raw)
In-Reply-To: <35D365A3D0D0487CB7928FB2A672541D@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <schwab@linux-m68k.org>, <11999@debbugs.gnu.org>
> Date: Fri, 20 Jul 2012 14:08:07 -0700
>
> > You will need to explain more, because info-insert-file-contents first
> > tests for the argument FILENAME, and if that does not exist, it tries
> > FILENAME with every extension in Info-suffix-list, which includes
> > ".info".
> >
> > In particular, this works for me on MS-Windows:
> > M-: (info-insert-file-contents "d:/path/to/emacs/info/emacs") RET
> > and loads emacs.info. Why doesn't it work for you?
>
> My bad. The difference turned out to be the use now of `user-error' instead of
> `error'. Where I previously just saw a message saying there was no such node,
> now Emacs puts me in the debugger, because I have non-nil `debug-on-error'.
So how is one supposed to avoid entering the debugger on user-error,
when debug-on-error is non-nil?
> Going only by the doc string of `user-error', it seems that at least some of the
> many changes from `error' to `user-error' in info.el (and beyond?) are
> inappropriate.
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).
Stefan, could you perhaps provide some insight? What is a "pilot
error" in this context, and how should Lisp programs use this new
facility to (supposedly) provide better diagnostics and/or better
error handling?
> An index lookup of a term that is not in the index is in general NOT a "pilot
> error". It is normal behavior on the part of users to look up terms in the
> index, whether they happen to be there or not.
I agree. But then it's unclear to me whether using 'error' in this
case would be better. If you think it is, please tell why.
> 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."
Agree again, but again unsure how 'error' would be better. Maybe we
need yet a 3rd kind of errors?
next prev parent reply other threads:[~2012-07-21 8:47 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 [this message]
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
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=83sjcl7b5w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11999@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).