From: "Drew Adams" <drew.adams@oracle.com>
To: 1478@emacsbugs.donarmstrong.com, 1478@debbugs.gnu.org
Subject: bug#1478: 23.0.60; doc string of custom-unlispify-*
Date: Sun, 10 Jul 2011 10:13:59 -0700 [thread overview]
Message-ID: <6341B9EB0F2F47EDAE765CD8E01F748A@us.oracle.com> (raw)
In-Reply-To: <002701c954da$22fdc570$0200a8c0@us.oracle.com>
1. I did not receive Lars's message explaining why he thinks this is not a bug.
Something wrong with the bug tracker? I received a `close' message that said
nothing more than it is closed. I had to go to the web site to see Lars's
message.
2. I disagree with everything Lars wrote about this bug.
a. This is about _doc strings_. It is not about the Customize UI.
b. `custom-unlispify-menu-entries': Please mention in the doc string what menu
is involved, and which menu entries.
c. `custom-unlispify-tag-names': No, this is not only "for (very special) people
who want to Customize low-level thingamabobs."
Just because you might not be interested in understanding this function, do not
assume that someone who wants to understand it intends to customize low-level
Customize thingamabobs.
I, as one user who wants to understand this, and who went to the trouble to file
a detailed bug report about missing info, do not know what is meant by a "tag"
in this context.
I have no intention of changing a tag (esp. since I don't even know what is
being referred to here by that name). But I want to understand this doc
string.
These doc strings are for users. So far, they are not comprehensible.
next prev parent reply other threads:[~2011-07-10 17:13 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
2011-07-10 17:13 ` Drew Adams [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6341B9EB0F2F47EDAE765CD8E01F748A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=1478@debbugs.gnu.org \
--cc=1478@emacsbugs.donarmstrong.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 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.