From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Jarek Czekalski <jarekczek@poczta.onet.pl>, 15670@debbugs.gnu.org
Subject: bug#15670: 24.3; dummy user-errors on info nodes without prev/next nodes
Date: Tue, 22 Oct 2013 03:17:53 +0200 [thread overview]
Message-ID: <87y55mayta.fsf@web.de> (raw)
In-Reply-To: <jwvd2my5z6k.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 21 Oct 2013 13:16:13 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > signal(user-error ("Node has no Next"))
> > user-error("Node has no %s" "Next")
> > ad-Orig-Info-extract-pointer("next" nil)
> > Info-extract-pointer("next")
> > Info-check-pointer("next")
> > redisplay_internal\ \(C\ function\)()
>
> > It's enough to start the info with C-h C-h r or C-h i to
> > make it happen.
>
> > Expected behaviour: no user-errors should be generated, when user makes
> > no errors.
>
> Hmm... indeed, but Info-check-pointer catches all errors:
>
> (defun Info-check-pointer (item)
> "Non-nil if ITEM is present in this node."
> (condition-case nil
> (Info-extract-pointer item)
> (error nil)))
>
> so that should silence this user-error.
> What am I missing?
Has anybody tried to reproduce this error? Note that the OP didn't hit
n for that to happen - it happend just while redisplaying. I don't see
this for emacs -Q. Could this be related to Emacsspeak?
Regards,
Michael.
next prev parent reply other threads:[~2013-10-22 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 15:32 bug#15670: 24.3; dummy user-errors on info nodes without prev/next nodes Jarek Czekalski
2013-10-21 15:52 ` bug#15670: how advised Jarek Czekalski
2013-10-21 16:43 ` bug#15670: 24.3; dummy user-errors on info nodes without prev/next nodes Drew Adams
2013-10-21 17:16 ` Stefan Monnier
2013-10-22 1:17 ` Michael Heerdegen [this message]
2013-10-22 5:47 ` Michael Heerdegen
2013-10-22 7:15 ` Jarek Czekalski
2013-10-23 7:51 ` Michael Heerdegen
2013-10-21 18:22 ` bug#15670: i'll try to get more info Jarek Czekalski
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=87y55mayta.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=15670@debbugs.gnu.org \
--cc=jarekczek@poczta.onet.pl \
--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).