From: "J.P." <jp@neverwas.me>
To: 73686@debbugs.gnu.org
Cc: emacs-erc@gnu.org
Subject: bug#73686: 31.0.50; ERC 5.6.1-git: back button gone from describe-face via erc-nicks-list-faces
Date: Tue, 08 Oct 2024 14:07:46 -0700 [thread overview]
Message-ID: <87y12y1exp.fsf__18822.6694169984$1728421755$gmane$org@neverwas.me> (raw)
In-Reply-To: <87ttdn5dsz.fsf@neverwas.me> (J. P.'s message of "Mon, 07 Oct 2024 23:06:20 -0700")
Small correction:
> From emacs -Q:
> 1. M-x list-faces-display RET
> 2. TAB TAB RET C-x o (but see below*)
^
Missing a C-x o here in the original recipe.
So I doubt this is directly related, but I'm noticing another
peculiarity regarding help buffers not named `*Help*'. As you'd expect,
going back via a back button replaces the window buffer with the
previous one. And though typing "l" does that as well, it also
re-creates the previous buffer in a new window, resulting in different
buffers with the same content (the new one being the default "*Help*").
From emacs -Q (on Emacs 30):
1. M-x list-faces-display RET
2. C-x o TAB TAB RET
3. In the help buffer for `abbrev-table-name':
<backtab> <backtab> RET
4. In the help buffer for `font-lock-function-name-face':
<backtab> RET
5. Back in `abbrev-table-name':
TAB RET (should take you back to "*Faces*")
Now start a new session, repeating 1-3. For 4, hit "l" instead, and
witness the unwanted default "*Help*" buffer pop up in another window.
Superficially, I think the disparity results from `help-xref-following'
being t in the base recipe (at the hands of `help-do-xref'):
* help-xref-go-back(#<buffer *Faces*>)
help-do-xref(nil help-xref-go-back (#<buffer *Faces*>))
help-button-action(#<marker (moves after insertion) at 751 in *Faces*>)
button-activate(#<marker (moves after insertion) at 751 in *Faces*> nil)
push-button(751)
Which allows for buffer reuse in `help-buffer'. No such arrangement
occurs with the "l" variant:
* help-xref-go-back(#<buffer *Faces*>)
help-go-back()
funcall-interactively(help-go-back)
next prev parent reply other threads:[~2024-10-08 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 2:47 bug#73686: 31.0.50; ERC 5.6.1-git: back button gone from describe-face via erc-nicks-list-faces J.P.
2024-10-08 6:06 ` J.P.
[not found] ` <87ttdn5dsz.fsf@neverwas.me>
2024-10-08 21:07 ` J.P. [this message]
[not found] ` <87y12y1exp.fsf@neverwas.me>
2024-10-08 23:41 ` J.P.
[not found] ` <87o73uyxgv.fsf@neverwas.me>
2024-10-09 0:59 ` J.P.
[not found] ` <8734l6xf91.fsf@neverwas.me>
2024-10-09 3:00 ` J.P.
2024-10-09 1:05 ` Dmitry Gutov
2024-10-09 1:24 ` J.P.
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='87y12y1exp.fsf__18822.6694169984$1728421755$gmane$org@neverwas.me' \
--to=jp@neverwas.me \
--cc=73686@debbugs.gnu.org \
--cc=emacs-erc@gnu.org \
/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).