unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: customize-apropos
Date: Tue, 13 Dec 2005 19:52:19 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICKEDFDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <200512140340.jBE3erw17431@raven.dms.auburn.edu>

      This message is shown if someone does `C-u M-x
      customize-apropos' - that's what we're discussing, right?

    Yes.  Actually, it is shown in four situations:

    1. As a result of a bug in some code.  (This is by far the most likely
       situation)

    2. If somebody uses C-M-c in the minibuffer (RET or C-j will not work)
       to get around the minibuffer completion functions which are
       designed to prevent such variables from being shown in a Custom
       buffer, unless the user is savvy enough to know how to override
       these completion functions.

    3. If the user calls M-x customize-variable or friends from Lisp
       instead of interactively, again in an attempt to override the
       completion functions.

    4. If somebody uses an obscure numeric arg, meant for expert users, to
       customize-apropos.

    These are all marginal situations.  We are talking about some very
    marginal aspect of Custom here, that is only going to be used
    _intentionally_ by experts.

Using a documented `C-u' with a standard command is not some bizarre expert
behavior. If this is not intended for users, then let's get rid of the `C-u'
option. I vote to keep it and clarify the Custom-buffer messages
accordingly, but if people think this `C-u' behavior is something for
experts only, then let's get rid of it.

The other cases might well correspond to a message such as you have
provided. It's unfortunate to lump together a message that responds to
obscure bugs ("the most likely situation") with a message that responds to a
user's `C-u'.

  reply	other threads:[~2005-12-14  3:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10  3:47 customize-apropos Luc Teirlinck
2005-12-10  3:51 ` customize-apropos Luc Teirlinck
2005-12-10 23:04 ` customize-apropos Kim F. Storm
2005-12-10 23:07   ` customize-apropos Luc Teirlinck
2005-12-11 16:49     ` customize-apropos Richard M. Stallman
2005-12-11  5:03 ` customize-apropos Richard M. Stallman
2005-12-11 17:57 ` customize-apropos Drew Adams
2005-12-12  5:03   ` customize-apropos Luc Teirlinck
2005-12-12  5:40     ` customize-apropos Drew Adams
2005-12-12 23:56       ` customize-apropos Luc Teirlinck
2005-12-13  0:22         ` customize-apropos Drew Adams
2005-12-13  0:45           ` customize-apropos Luc Teirlinck
2005-12-13  3:55             ` customize-apropos Drew Adams
2005-12-13  1:01           ` customize-apropos Luc Teirlinck
2005-12-13  1:29           ` customize-apropos Luc Teirlinck
2005-12-13 23:33         ` customize-apropos Richard M. Stallman
2005-12-14  1:14           ` customize-apropos Luc Teirlinck
2005-12-14  1:25             ` customize-apropos Drew Adams
2005-12-14  2:13               ` customize-apropos Luc Teirlinck
2005-12-14  3:20                 ` customize-apropos Drew Adams
2005-12-14  3:40                   ` customize-apropos Luc Teirlinck
2005-12-14  3:52                     ` Drew Adams [this message]
2005-12-14  5:58                       ` customize-apropos Luc Teirlinck
2005-12-14 15:07                         ` customize-apropos Drew Adams
2005-12-15  5:33                           ` customize-apropos Luc Teirlinck
2005-12-15 16:33                             ` customize-apropos Drew Adams
2005-12-16  5:09                               ` customize-apropos Richard M. Stallman
2005-12-14  3:45                   ` customize-apropos Luc Teirlinck
2005-12-14  3:54                     ` customize-apropos Drew Adams
2005-12-14 20:02             ` customize-apropos Richard M. Stallman
2005-12-15  4:18               ` customize-apropos Luc Teirlinck
2005-12-16  1:51                 ` customize-apropos Richard M. Stallman
2005-12-16  3:47                   ` customize-apropos Luc Teirlinck

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=DNEMKBNJBGPAOPIJOOICKEDFDAAA.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).