From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 7385@debbugs.gnu.org
Subject: bug#7385: 24.0.50; Please index defcustom type constructs
Date: Fri, 12 Nov 2010 19:03:10 +0200 [thread overview]
Message-ID: <83hbfmeapd.fsf@gnu.org> (raw)
In-Reply-To: <F8CE95A6B21C449BAB5C423CA8662B58@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Fri, 12 Nov 2010 08:29:18 -0800
> Cc:
>
> In the Elisp manual, you should be able to do `i restricted-sexp RET' to
> go to the section that explains that defcustom type construct. Likewise
> for the other type constructs.
Such indexing is not useful, IMO. If you already know that you are
looking for restricted-sexp, you can use `s restricted-sexp RET'.
With such a specialized string, chances that you will get too many
false hits are nil. Alternatively, go to the chapter and look through
its sections.
Indexing is mainly for readers who do NOT know what they are after.
It would be much more useful if you (or someone else) could come up
with some phrase that could be on the reader's mind when she is after
these features. Currently, the section where they are documented has
only one index entry: "composite types (customization)". Suggestions
for more are most welcome.
next prev parent reply other threads:[~2010-11-12 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 16:29 bug#7385: 24.0.50; Please index defcustom type constructs Drew Adams
2010-11-12 17:03 ` Eli Zaretskii [this message]
2010-11-12 18:32 ` Drew Adams
2010-11-12 21:08 ` Stefan Monnier
2010-11-13 7:47 ` MON KEY
2010-11-13 8:06 ` Eli Zaretskii
2010-11-13 8:09 ` Eli Zaretskii
2010-11-13 8:39 ` MON KEY
2010-11-13 13:57 ` Eli Zaretskii
2016-04-27 22:53 ` 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
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=83hbfmeapd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7385@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).