From: Eli Zaretskii <eliz@gnu.org>
To: MON KEY <monkey@sandpframing.com>
Cc: 7385@debbugs.gnu.org
Subject: bug#7385: 24.0.50; Please index defcustom type constructs
Date: Sat, 13 Nov 2010 15:57:26 +0200 [thread overview]
Message-ID: <838w0xe37d.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTinUej4zjJgOBKnqFNu8iELX69w6BeHXR1MD58eV@mail.gmail.com>
> Date: Sat, 13 Nov 2010 03:39:19 -0500
> From: MON KEY <monkey@sandpframing.com>
> Cc: 7385@debbugs.gnu.org, Drew Adams <drew.adams@oracle.com>
>
> On Sat, Nov 13, 2010 at 3:09 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> >> Such handlists exist because I routinely can't find what I am looking
> >> for in the manual.
> >
> > Please report every one of them as a documentation bug.
> >
>
> I prob. should have qualified the above.
> To be clear, what I meant to communicate was this:
>
> I routinely have trouble knowing what to look for and where to do it
> when I can't immediately find something in the manuals.
>
> Indeed, FTMP the manuals _do_ provide the information one requires.
> It just isn't always easily at hand.
>
> I don't think this constitutes a bug. Do you?
It could be. Here's how to know: Whenever you are looking for some
issue, think about a word or a phrase of several words, which would
(in your opinion) be appropriate as index entries, or parts of index
entries, for that issue. Then try these words/phrases with the `i'
command. If they don't get you to the section of the manual where the
issue is described, submit a docs bug report and be sure to mention
the phrases you used to search.
TIA
next prev parent reply other threads:[~2010-11-13 13:57 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838w0xe37d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7385@debbugs.gnu.org \
--cc=monkey@sandpframing.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.