From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 1478@debbugs.gnu.org
Subject: bug#1478: 23.0.60; doc string of custom-unlispify-*
Date: Sun, 10 Jul 2011 14:57:14 +0200 [thread overview]
Message-ID: <m3ei1yguol.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <002701c954da$22fdc570$0200a8c0@us.oracle.com> (Drew Adams's message of "Tue, 2 Dec 2008 16:00:21 -0800")
"Drew Adams" <drew.adams@oracle.com> writes:
> 1. The doc string of `custom-unlispify-menu-entries' says only this:
>
> "Display menu entries as words instead of symbols if non-nil."
>
> What menu entries? Which menu?
>
> It took me a while, searching and experimenting, to find that this is
> about the `Custom' menu's submenus. Please clarify what this is for in
> the doc string.
I disagree. The grouping is `custom-menu', so what else could it be
referring to? This would be like if all dired variables and commands
had doc strings starting with "In Dired...".
> 2. The doc string of `custom-unlispify-tag-names' says only this:
>
> "Display tag names as words instead of symbols if non-nil."
>
> What's a tag name? This won't make much sense to an Emacs user who isn't savvy
> to Emacs Lisp, `defcustom' :type, and :tag. Please explain this
> better. A simple illustrative example never hurts: show what happens if
> it's nil vs if it's non-nil.
This is for (very special) people who want to customize the Customize
low-level thingamabobs. I think they probably know what a tag is, if
they want to change it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-10 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 0:00 bug#1478: 23.0.60; doc string of custom-unlispify-* Drew Adams
2011-07-10 12:57 ` Lars Magne Ingebrigtsen [this message]
2011-07-10 17:13 ` Drew Adams
2011-07-10 17:22 ` Drew Adams
2011-08-02 16:10 ` Lars Magne 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
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=m3ei1yguol.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=1478@debbugs.gnu.org \
--cc=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).