all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Bastien'" <bzg@altern.org>,
	"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 13276@debbugs.gnu.org, rms@gnu.org
Subject: bug#13276: 24.2.50; apropos-variable
Date: Sat, 5 Jan 2013 09:52:23 -0800	[thread overview]
Message-ID: <875D2690F3D44FF4B693C744AB397051@us.oracle.com> (raw)
In-Reply-To: <87pq1kc4eo.fsf@bzg.ath.cx>

> >> I suggest renaming `apropos-variable' to `apropos-option' and to
> >> use `apropos-variable' for 
> > That sounds right.
> The attached patch does this.

Glad to see this finally happening.

> It renames `apropos-variable' to `apropos-option' and define a new
> `apropos-variable' command.  C-u M-x apropos-variable RET shows only
> user options, and C-u M-x apropos-option RET shows all variables.
> 
> The patch also introduces a new button for user options so that
> users can immediately see which variables are options in the apropos
> buffer.

IOW, essentially the code I pointed to last month (as well as years ago):
http://www.emacswiki.org/emacs/download/apropos-fn%2bvar.el


FWIW, this doc line is not too good:

 With \\[universal-argument] prefix, or if `apropos-do-all' is non-nil, also
show
-normal variables."
+variables, not just user options."

User options _are_ variables.  The line should say something like "also show
variables that are not user options."


Question (not particularly related to this patch):

Why do we treat the faces differently for, say, `apropos-symbol' and
`apropos-variable'?

apropos.el defines faces for these buttons:

apropos-function-button
apropos-variable-button
apropos-option-button
apropos-misc-button

But it defines faces for these things - not for their buttons:

apropos-symbol
apropos-keybinding
apropos-property

Why don't we handle the following the same way we handle `apropos-symbol' (or
vice versa):

apropos-function
apropos-variable
apropos-option
apropos-misc

E.g., when defining their button types, just include both `button' and the
thing's face for property `face'?  E.g.,

(defface apropos-option '((t (:inherit font-lock-variable-name-face)))
  "Face used for option names in Apropos buffers."
  :group 'apropos)

(define-button-type 'apropos-option
  'apropos-label "Option"
  'apropos-short-label "o"
  'face '(apropos-option button)  ; <======================
  'help-echo "mouse-2, RET: Display more help on this user option (variable)"
  'follow-link t
  'action (lambda (button)
            (describe-variable (button-get button 'apropos-symbol))))

Just wondering.  Why do we treat these differently?  In all cases the faces are
used only for buttons.  Is there some advantage to using one or the other
treatment?  Thx.






  reply	other threads:[~2013-01-05 17:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-25  5:35 bug#13276: 24.2.50; apropos-variable Richard Stallman
2012-12-26 11:10 ` Bastien
2012-12-26 16:56   ` Drew Adams
2013-01-04  1:40 ` Glenn Morris
2013-01-04  7:54   ` Bastien
2013-01-04 17:52     ` Stefan Monnier
2013-01-04 19:03       ` Drew Adams
2013-01-05 10:25       ` Bastien
2013-01-05 17:52         ` Drew Adams [this message]
2013-01-05 19:11         ` Glenn Morris
2013-01-07 22:04           ` Bastien
2013-01-08  4:31             ` Glenn Morris
2013-01-08  7:15               ` Bastien
2013-01-05 23:40         ` Stefan Monnier
2013-01-07 22:04           ` Bastien
2013-01-08 14:11           ` Drew Adams
2013-01-08 14:33             ` Bastien
2013-01-08 14:38               ` Drew Adams
2013-01-08 15:48                 ` Drew Adams
2013-01-08 16:05                   ` Bastien
2013-01-08 16:56                     ` Drew Adams
2013-01-08 17:53                       ` Bastien
     [not found]                       ` <<87fw2bh881.fsf@bzg.ath.cx>
2014-04-21 18:35                         ` Drew Adams
2014-04-22  9:31                           ` Bastien
2013-01-04 20:00     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875D2690F3D44FF4B693C744AB397051@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13276@debbugs.gnu.org \
    --cc=bzg@altern.org \
    --cc=monnier@iro.umontreal.ca \
    --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 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.