all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liang-Jie Lee <s930054123yaoyao@gmail.com>
To: 55376@debbugs.gnu.org
Subject: bug#55376: Inconsistent behavior in apropos-user-options
Date: Thu, 12 May 2022 02:38:40 +0800	[thread overview]
Message-ID: <CAB+tG3utWgK1UsPCRVJiX=OT-fvv-W_uEF7v-GRw8420wAWzew@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1033 bytes --]

According to the manual, apropos-user-option can search not only user
options but variables when adding C-u prefix.
> With C-u prefix, or if ‘apropos-do-all’ is non-nil, also show variables,
not just user options.

From the documentation, I think using C-u should have the same effect as
setting apropos-do-all to t. But my experiment got 2 different results.

1. set apropos-do-all to t
(let ((apropos-do-all t))
  (call-interactively #'apropos-user-option))

Insert "emacs", and I got the result shown in figure 1. In the Apropos
buffer, each variable has a hyperlink to the corresponding *help* buffer.

2. C-u M-x apropos-user-option, and insert "emacs"
The result is shown in figure 2. As you can see, those entries have no
hyperlinks to the documentation.

I think the behavior is not consistent compared to other apropos commands.
For example, no matter using method 1 or 2 to invoke apropos-commands (C-h
a), we would get 2 same buffers both with hyperlinks to click off.

Regards,
Liang-Jie Lee

[-- Attachment #1.2: Type: text/html, Size: 1271 bytes --]

[-- Attachment #2: 1.png --]
[-- Type: image/png, Size: 209202 bytes --]

[-- Attachment #3: 2.png --]
[-- Type: image/png, Size: 182467 bytes --]

             reply	other threads:[~2022-05-11 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 18:38 Liang-Jie Lee [this message]
2022-05-11 23:49 ` bug#55376: Inconsistent behavior in apropos-user-options 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='CAB+tG3utWgK1UsPCRVJiX=OT-fvv-W_uEF7v-GRw8420wAWzew@mail.gmail.com' \
    --to=s930054123yaoyao@gmail.com \
    --cc=55376@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 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.