From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: 33830@debbugs.gnu.org
Subject: bug#33830: 27.0.50; help-xref-stack contains bad entries
Date: Wed, 23 Jun 2021 15:58:12 +0200 [thread overview]
Message-ID: <87h7holm2z.fsf@gnus.org> (raw)
In-Reply-To: <87sgyqyg2o.fsf@gmail.com> (Alex Branham's message of "Fri, 21 Dec 2018 10:55:59 -0600")
Alex Branham <alex.branham@gmail.com> writes:
> Sometimes `help-xref-stack' contains "bad" entries, which makes
> help-go-forward and help-go-back error in a strange way. To see what I
> mean:
>
> emacs -q
>
> C-h f car RET
> C-h k C-x t
> C-h f cdr RET
>
> Now that the *Help* buffer is displaying `cdr', if you try to go back
> (with "l" or clicking the back button), you get "user-error C-x t is
> undefined".
This doesn't exactly reproduce for me in Emacs 27.1, because `C-x t' is
bound there. But this works:
C-h f car RET
C-h k C-x t t
C-h f cdr RET
C-x o
l
I do get the "is undefined" message, but then hitting `l' again takes me
back to `car'.
I guess it could make sense for `l'/`r' to skip these "invalid" entries,
but on the other hand, I can see how they'd be vaguely useful.
Does anybody have any opinions here?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-06-23 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 16:55 bug#33830: 27.0.50; help-xref-stack contains bad entries Alex Branham
2018-12-27 22:38 ` Federico Tedin
2021-06-23 13:58 ` Lars Ingebrigtsen [this message]
2021-07-22 14:20 ` Lars Ingebrigtsen
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=87h7holm2z.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=33830@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
/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).