From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Christoph Scholtes <cschol2112@googlemail.com>, 8327@debbugs.gnu.org
Subject: bug#8327: 24.0.50; Info mode manual: headline of section 1.4 is confusing
Date: Thu, 14 Jul 2011 21:14:08 +0200 [thread overview]
Message-ID: <m3ei1sisjj.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <834o6uv5oi.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 23 Mar 2011 06:09:33 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Shouldn't it be
>>
>> @section The Space, DEL, b and C-l commands
>>
>> to match the actual commands referred to in the text?
>
> Not sure. This manual is used for the stand-alone Info, whose users
> might not know what C-l is.
There's a bunch of other C-<key> things in the manual. For instance,
that very node says:
---
@kindex C-l @r{(Info mode)}
If your screen is ever garbaged, you can tell Info to display it
again by typing @kbd{C-l} (@kbd{Control-L}---that is, hold down
@key{CTRL} and type @kbd{L} or @kbd{l}).
---
However, it's a very meta node, which starts off with:
---
@node Help-^L, Help-Inv, Help-P, Getting Started
@comment node-name, next, previous, up
@section The Space, DEL, B and ^L commands
This node's mode line tells you that you are now at node
@samp{Help-^L}, and the header line tells you that @kbd{p} would get
you back to @samp{Help-P}. The node's title is highlighted and may be
underlined as well; it says what the node is about.
---
What on earth is "Help-^L" meant to signify? I have no idea. The
author probably knows.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-14 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 0:51 bug#8327: 24.0.50; Info mode manual: headline of section 1.4 is confusing Christoph Scholtes
2011-03-23 4:09 ` Eli Zaretskii
2011-07-14 19:14 ` Lars Magne Ingebrigtsen [this message]
2011-07-14 19:34 ` Eli Zaretskii
2011-07-14 20:21 ` Lars Magne Ingebrigtsen
2011-07-15 6:00 ` Eli Zaretskii
2011-09-11 3:49 ` 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=m3ei1sisjj.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=8327@debbugs.gnu.org \
--cc=cschol2112@googlemail.com \
--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).