From: Federico Tedin <federicotedin@gmail.com>
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: Thu, 27 Dec 2018 19:38:59 -0300 [thread overview]
Message-ID: <874layegsc.fsf@gmail.com> (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".
>
> Alex
I've noticed that the `describe-key' and `describe-function' functions both
call `help-setup-xref' with key sequences and functions respectively,
even if said key sequences or functions are not valid (i.e. when the key
sequence isn't bound to anything and the function does not exist).
An example of this:
1) M-:: (describe-function 'hello) RET
2) C-h f car RET
3) On the *Help* buffer, press 'l'
The message 'Symbol’s function definition is void: hello' will be
displayed, and the *Help* buffer will contain "hello is ". Also, for
some reason, after pressing 'r', two [back] buttons will be shown.
Maybe `help-setup-xref' should only be called when it is certain that
the key sequence/function/etc. exists?
(tested on master branch)
next prev parent reply other threads:[~2018-12-27 22:38 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 [this message]
2021-06-23 13:58 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874layegsc.fsf@gmail.com \
--to=federicotedin@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.