From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 44909@debbugs.gnu.org
Subject: bug#44909: Hyperlinks gone for first story of two-storied *Help* buffers
Date: Sat, 28 Nov 2020 03:13:54 +0800 [thread overview]
Message-ID: <87o8jid34d.5.fsf@jidanni.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 35 bytes --]
Look at this weird *Help* screen,
[-- Attachment #2: Ugly --]
[-- Type: image/png, Size: 25910 bytes --]
[-- Attachment #3: Type: text/plain, Size: 1200 bytes --]
Note the four non-hyperlinked items?
> How did you get that, Jacobson?
> I can't get such a two-storied *Help* buffer with either C-h f nor C-h v.
> Are you taking the wrong prescption drugs?
It's a long story:
$ emacs -Q
C-h f ;; describe-function
s ;; self-insert-command
o ;; self-insert-command
- ;; self-insert-command
l ;; self-insert-command
o ;; self-insert-command
n ;; self-insert-command
g ;; self-insert-command
<return> ;; minibuffer-complete-and-exit
C-x o ;; other-window
<tab> ;; forward-button
<tab> ;; forward-button
<return> ;; push-button
C-x 1 ;; delete-other-windows
C-h l ;; view-lossage
Yes, the cursor was on top of
‘global-so-long-mode’
when I did push-button.
Because global-so-long-mode is both a function and a variable, I get the
two-storied *Help* window.
But whoever invented two-storied *Help* windows didn't make sure all the
hyperlinks are hyperlinked.
Sure they are when you do
(describe-function 'global-so-long-mode)
(describe-variable 'global-so-long-mode)
individually. But not when you do them "both at the same time" via the
push-button.
emacs-version "27.1"
next reply other threads:[~2020-11-27 19:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 19:13 積丹尼 Dan Jacobson [this message]
2020-11-28 7:39 ` bug#44909: Hyperlinks gone for first story of two-storied *Help* buffers Eli Zaretskii
2020-11-28 7:56 ` Stefan Kangas
2011-06-28 16:38 ` bug#8951: 24.0.50; [PATCH] enhancement request: buttonize key names Drew Adams
2011-07-04 20:28 ` Stefan Monnier
2011-07-04 21:08 ` Drew Adams
2011-07-06 18:49 ` Stefan Monnier
2011-07-06 19:55 ` Drew Adams
2011-07-08 19:07 ` Stefan Monnier
2011-07-08 19:20 ` Drew Adams
2019-06-27 16:35 ` Lars Ingebrigtsen
2021-10-23 0:46 ` Stefan Kangas
2021-10-24 13:36 ` Lars Ingebrigtsen
2021-10-24 13:54 ` Stefan Kangas
2021-10-24 14:15 ` Lars Ingebrigtsen
2021-10-24 14:56 ` Stefan Kangas
2021-10-24 21:07 ` bug#8951: [External] : " Drew Adams
2021-10-24 21:37 ` Stefan Kangas
2021-10-24 22:05 ` Drew Adams
2021-10-24 22:24 ` Stefan Kangas
2021-10-24 22:47 ` Drew Adams
2021-10-24 23:15 ` Stefan Kangas
2021-10-25 1:32 ` Drew Adams
2021-10-25 2:37 ` Stefan Kangas
2020-11-28 20:45 ` bug#8951: bug#44909: Hyperlinks gone for first story of two-storied *Help* buffers 積丹尼 Dan Jacobson
2020-11-29 10:25 ` 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=87o8jid34d.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=44909@debbugs.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).