unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Systematic implicit aliases for option variables
Date: Wed, 02 Mar 2022 13:01:51 +0200	[thread overview]
Message-ID: <83sfs0k480.fsf@gnu.org> (raw)
In-Reply-To: <E1nPGt1-0002mX-Pm@fencepost.gnu.org> (message from Richard Stallman on Tue, 01 Mar 2022 23:46:51 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Tue, 01 Mar 2022 23:46:51 -0500
> 
>   > > 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.

Yes, it currently only considers names.  The idea is to extend it
consider aliases as well.  For example, for each symbol it finds by
name, it could attempt to find its alias(es), and if found, show the
symbols related to those aliases as well.  Similar to what you
suggested, but without a new command.



  reply	other threads:[~2022-03-02 11:01 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
2022-03-02 11:01     ` Eli Zaretskii [this message]
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=83sfs0k480.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).