all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "N. Jackson" <nljlistbox2@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 16455@debbugs.gnu.org
Subject: bug#16455: 24.3; (Emacs Info) h command behaves like H command
Date: Wed, 15 Jan 2014 16:45:26 -0400	[thread overview]
Message-ID: <CABcSQd5hug=gWYUCmJ0ksC7W3yoNi4drE6FxwAKFy2rE+q2qDw@mail.gmail.com> (raw)
In-Reply-To: <p0k3e1b299.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2996 bytes --]

On 2014-01-15 13:09, Glenn Morris wrote:
> Hmm, yet the info page for info says:
>
>     If you are new to the Info reader and want to learn how to use it,
>     type the command `h' now.  It brings you to a programmed instruction
>     sequence.

Indeed, from the command line the command "info info" pulls up a node
containing this exact text. However pressing H brings up the tutorial
whereas pressing h actually brings up the help page with the keyboard
commands that is promised by the man page and which I'm also trying
to get to by pressing h in the Emacs Info viewer.

This incredibly useful page (it is identified in the status line as
"Info: *Info Help*") begins:

   Basic Info command keys

   x           Close this help window.
   q           Quit Info altogether.
   H           Invoke the Info tutorial.

   Up          Move up one line.
   Down        Move down one line.
   DEL         Scroll backward one screenful.
   SPC         Scroll forward one screenful.
   Home        Go to the beginning of this node.
   End         Go to the end of this node.

   TAB         Skip to the next hypertext link.
   RET         Follow the hypertext link under the cursor.
   l           Go back to the last node seen in this window.

   [           Go to the previous node in the document.
   ]           Go to the next node in the document.
   p           Go to the previous node on this level.
   n           Go to the next node on this level.
   u           Go up one level.
   t           Go to the top node of this document.
   d           Go to the main `directory' node.

   1...9       Pick the first...ninth item in this node's menu.
   0           Pick the last item in this node's menu.
   m           Pick a menu item specified by name.
   r           Follow a cross reference specified by name.
   g           Go to a node specified by name.

   s           Search forward for a specified string.
   {           Search for previous occurrence.
   }           Search for next occurrence.
   i           Search for a specified string in the index, and
                 select the node referenced by the first entry found.
   I           Synthesize menu of matching index entries.

   C-g         Cancel the current operation.

Note the

   H           Invoke the Info tutorial.

And also much further down the list of keys, it says (under the
heading "Commands available in Info windows:")

   H       (get-info-help-node)Visit Info node `(info)Help'

and

   h       (get-help-window)Display help message

Clearly there are inconsistencies / documentation bugs in Info.

As far as Emacs goes though, if h rather than H is *intended* to bring
up the tutorial (which it does), then there is not an Emacs bug here,
unless there is no way to get to the list of keyboard commands (which
is arguably *the* most important page in the Info documentation). Would
it not seem to be a flaw in the Emacs Info viewer if it is not easy to
get to this information, and obvious how to do so?

[-- Attachment #2: Type: text/html, Size: 3388 bytes --]

  reply	other threads:[~2014-01-15 20:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 15:28 bug#16455: 24.3; (Emacs Info) h command behaves like H command N. Jackson
2014-01-15 17:09 ` Glenn Morris
2014-01-15 20:45   ` N. Jackson [this message]
2014-01-15 21:16     ` Glenn Morris
2014-01-16  3:03       ` N. Jackson
2014-01-16  3:15         ` N. Jackson
2014-01-16  8:28         ` Glenn Morris
2014-01-16 16:25           ` N. Jackson
2014-02-28  2:17             ` Glenn Morris

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='CABcSQd5hug=gWYUCmJ0ksC7W3yoNi4drE6FxwAKFy2rE+q2qDw@mail.gmail.com' \
    --to=nljlistbox2@gmail.com \
    --cc=16455@debbugs.gnu.org \
    --cc=rgm@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 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.