all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: karl@freefriends.org (Karl Berry)
Subject: [alinoe@xl.wp.pl: The L command described too late]
Date: Sun, 20 Aug 2006 16:24:28 -0500	[thread overview]
Message-ID: <200608202124.k7KLOSN28296@f7.net> (raw)

I tend to agree with the user's suggestion below.  I personally use l
more than nearly anything else besides SPC.

So I suggest we create a new node for it, between these two:
    @section The Space, DEL, B and ^L commands
    @section Invisible text in Emacs Info

And move the help text from the end of the SPC node to the new node.
That will also have the advantage of making the SPC node a little
shorter; it's quite long.

Ok?  (I'm happy to make the actual change, but since we've discussed the
Info manual so extensively here, thought I should bring it up first.)

As a separate issue, the node name Help-^L for the SPC node would be
better as "Help-Move" or some such.  I surmise that Help-^L just looks
gobbeldygook to some new users trying to read through the tutorial.

Thanks,
Karl


Date: Sat, 19 Aug 2006 21:55:17 +0200
From: Alinoe <alinoe@xl.wp.pl>
To: help-texinfo@gnu.org
Subject: [help-texinfo] The L command described too late

Hi

I have one remark about the texinfo documentation for Info. Namely, the 
small-L (last) command is described in "Intermediate Info commands" node, 
while it is, IMHO, a very basic and very useful command. I suggest describing 
it earlier, somewhere after P, N and SPACE, but before the menus.

Before learning the L command I often got lost in the hierarchy of nodes and 
had to start all over from the beginning in order to come back where I was 
before.

BR
Tom

             reply	other threads:[~2006-08-20 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-20 21:24 Karl Berry [this message]
2006-08-27 19:43 ` [alinoe@xl.wp.pl: The L command described too late] Juri Linkov

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=200608202124.k7KLOSN28296@f7.net \
    --to=karl@freefriends.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 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.