From: "Drew Adams" <drew.adams@oracle.com>
To: 9117@debbugs.gnu.org
Subject: bug#9117: 24.0.50; Document menu keyword `:selected'
Date: Mon, 18 Jul 2011 09:23:41 -0700 [thread overview]
Message-ID: <3D2F66922B1E45A2888485C8E28AADB3@us.oracle.com> (raw)
Please document the menu keyword :selected. Presumably the place for
this would be: `(elisp) Extended Menu Items', along with :visible,
:enable, etc.
In particular, document its relation with keywords such as :visible and
:enable - e.g., if not visible then :selected is not evaluated (or
whatever is the truth).
For example, I see code such as this in a 3rd-party library, and I
wonder what happens if `ls-lisp-dirs-first' is undefined. The :visible
sexp here is protected OK (by `ls-lisp-var-p'), but if :selected is
eval'd even when :visible is nil then this would presumably raise an
error.
["Ignore Case" dired-sort-menu-toggle-ignore-case :style toggle
:selected ls-lisp-ignore-case :active t
:help "Ignore case in alphanumeric sorting"
;; supported only by (Emacs 21) ls-lisp library and local dired:
:visible (ls-lisp-var-p 'ls-lisp-ignore-case)]
["Dirs First" dired-sort-menu-toggle-dirs-first :style toggle
:selected ls-lisp-dirs-first :active t
:help "List subdirectories first [last if reversed]"
;; supported only by (Emacs 21) ls-lisp library and local dired:
:visible (ls-lisp-var-p 'ls-lisp-dirs-first)]
Anyway, the point is that there seems to be no documentation at all for
:selected, even though it is used in lots of core Lisp code and in
3rd-party code.
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2011-07-11 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt --cflags
-Ic:/build/include'
next reply other threads:[~2011-07-18 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 16:23 Drew Adams [this message]
2011-09-11 3:14 ` bug#9117: 24.0.50; Document menu keyword `:selected' Lars Magne Ingebrigtsen
2016-04-28 11:12 ` Lars Ingebrigtsen
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=3D2F66922B1E45A2888485C8E28AADB3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9117@debbugs.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.