unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: command to customize the thing at point?
Date: Wed, 22 Feb 2006 07:23:23 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICEEPGDCAA.drew.adams@oracle.com> (raw)
In-Reply-To: <7dbe73ed0602220211s72411e09v609793ab5e5adfff@mail.gmail.com>

    > How about having a single command that would call customize-face,
    > customize-option, or customize-group, as appropriate, on the
    > name at point or under the mouse pointer?

    In what contexts/places would it be useful?

Any context in which, today, you might use `customize-face',
`customize-option', or `customize-group'. These are essentially just
different manifestations of the same `customize' method applied to different
kinds of "objects".

The point is that you're already pointing at the name of the thing in
question (via point or mouse pointer), and that "object" should "know" what
the "method" `customize' means to it (to descend to oopspeak).

(No, I'm not advocating any oopness for Emacs here; I just thought that
phrasing it ooply might make the point clearer to those born post Oop (other
than Alley, that is).)

In only relatively few cases is the object in question ambiguous; in those
cases, the command would ask you which is the intended target. It could
either ask you explicitly (y/n) or just let you cycle through the possible
values ("foo (function)", "foo (option)", "foo (face)").

The same idea might be used for `describe-variable', `describe-function',
etc. when it picks up the default value - much of the time the name is
unambiguous.

This could mean fewer keys to learn for gnubees.

  reply	other threads:[~2006-02-22 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 21:57 command to customize the thing at point? Drew Adams
2006-02-22 10:11 ` Mathias Dahl
2006-02-22 15:23   ` Drew Adams [this message]
2006-02-24  0:32     ` Juri Linkov
2006-02-25  7:57     ` Mathias Dahl
2006-02-25 16:28       ` Drew Adams

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=DNEMKBNJBGPAOPIJOOICEEPGDCAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /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).