From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15810@debbugs.gnu.org
Subject: bug#15810: 24.3.50; inappropriate text in (emacs) `Echo Area'
Date: Tue, 5 Nov 2013 09:14:35 -0800 (PST) [thread overview]
Message-ID: <8439332c-eb08-4dc1-bed9-c947baa68903@default> (raw)
In-Reply-To: <<831u2u94af.fsf@gnu.org>>
> > This text has no business being there:
> >
> > (We have not explained buffers yet; see *note Buffers::,
> > for more information about them.)
>
> It is appropriate for when the manual is read as a book, linearly.
It is unnecessary in that rare case. And it is inappropriate in
the far more common (in fact, typical) case: when the passage is
not read after reading all of the text linearly, starting from
page one.
Read the bug report, which says that it is not appropriate for the
*hypertext* manual. Leave it in for the printed manual, if you like
(though even there it is not needed - a forward cross reference
should stand on its own).
> (We have not explained variables either; see *note Variables::,
> for more information about them.)
>
> Irrelevant.
What is irrelevant? The quoted text from the manual? Yes, except
for the cross reference it is irrelevant - no, worse, it is
misleading and can confuse.
> This is not a bug, closing.
It is a bug. Such text simply does not belong in hypertext doc.
The cross references should remain. The verbiage about your not
having explained XXXX yet is not appropriate for hypertext doc.
(And you should know that by now.)
Reopening.
next parent reply other threads:[~2013-11-05 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<6e7c805d-a5fe-499b-9a1c-e0ee1e81dec9@default>
[not found] ` <<831u2u94af.fsf@gnu.org>
2013-11-05 17:14 ` Drew Adams [this message]
2013-11-05 17:20 ` bug#15810: 24.3.50; inappropriate text in (emacs) `Echo Area' Glenn Morris
2013-11-05 17:20 ` Eli Zaretskii
2013-11-05 15:39 Drew Adams
2013-11-05 16:55 ` Eli Zaretskii
2013-11-05 19:30 ` Stefan Monnier
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=8439332c-eb08-4dc1-bed9-c947baa68903@default \
--to=drew.adams@oracle.com \
--cc=15810@debbugs.gnu.org \
--cc=eliz@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 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).