From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18281@debbugs.gnu.org
Subject: bug#18281: 24.4.50; doc of `customize-apropos*'
Date: Sat, 3 Aug 2019 14:11:27 -0700 (PDT) [thread overview]
Message-ID: <0d357ba7-59d2-41ea-843f-88d1f2217d13@default> (raw)
In-Reply-To: <871ry2f5cc.fsf@mouse.gnus.org>
> > If you provide a list of words then all possible pairs of the words
> > are matched together, in both orders, against the name of each
> > Customize object of TYPE. That is, the object name must contain
> > both words as substrings.
>
> I don't know what the doc string said at the time you filed the report
> (it would be helpful if you included that in your reports),
The build reported is the one the report is about.
(That's why build info is included.) And yes, that
was 5 years ago...
A guess is that it said the same thing that is said
in Emacs 23.4 - just this:
customize-apropos is an interactive autoloaded Lisp function in
`cus-edit.el'.
It is bound to <menu-bar> <options> <customize> <customize-apropos>.
(customize-apropos REGEXP &optional ALL)
Customize all loaded options, faces and groups matching REGEXP.
If ALL is `options', include only options.
If ALL is `faces', include only faces.
If ALL is `groups', include only groups.
If ALL is t (interactively, with prefix arg), include variables
that are not customizable options, as well as faces and groups
(but we recommend using `apropos-variable' instead).
> but currently it says:
>
> Customize loaded options, faces and groups matching PATTERN.
> PATTERN can be a word, a list of words (separated by spaces),
> or a regexp (using some regexp special characters). If it is a word,
> search for matches for that word as a substring. If it is a list of
> words, search for matches for any two (or more) of those words.
Good.
prev parent reply other threads:[~2019-08-03 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 18:11 bug#18281: 24.4.50; doc of `customize-apropos*' Drew Adams
2019-08-03 18:53 ` Lars Ingebrigtsen
2019-08-03 21:11 ` Drew Adams [this message]
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=0d357ba7-59d2-41ea-843f-88d1f2217d13@default \
--to=drew.adams@oracle.com \
--cc=18281@debbugs.gnu.org \
--cc=larsi@gnus.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.