From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Systematic implicit aliases for option variables
Date: Tue, 01 Mar 2022 23:46:51 -0500 [thread overview]
Message-ID: <E1nPGt1-0002mX-Pm@fencepost.gnu.org> (raw)
In-Reply-To: <9F2080B9-A7FE-4E7B-9920-8368A9D6DEBE@gnu.org> (message from Eli Zaretskii on Tue, 01 Mar 2022 10:08:01 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > If you give it `occur', it would recognize that that is an alias
> > for `list-matching-lines', and show you the options pertinent to
> > `list-matching-lines'. You wouldn't need to know that `occur'
> > is an alias.
> >
> > I think the hard part of this would be adding a data base to find the
> > custom groups that are pertinent to any particular command.
> >
> Sounds like a natural extension of customize-apropos, which we already have?
Could you explain how it relates to customize-apropos? That selects
options purely on their names -- the feature I request would select
them based on semantics.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-03-02 4:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 4:24 Systematic implicit aliases for option variables Richard Stallman
2022-03-01 8:08 ` Eli Zaretskii
2022-03-02 4:46 ` Richard Stallman [this message]
2022-03-02 11:01 ` Eli Zaretskii
2022-03-03 5:08 ` Richard Stallman
2022-03-01 17:43 ` [External] : " Drew Adams
2022-03-03 5:05 ` Richard Stallman
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=E1nPGt1-0002mX-Pm@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).