all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs manual
Date: Wed, 08 Apr 2009 17:35:16 +0300	[thread overview]
Message-ID: <83vdpf43iz.fsf@gnu.org> (raw)
In-Reply-To: <87tz4zmfn6.fsf@gmail.com>

> From: Sean Sieger <sean.sieger@gmail.com>
> Date: Wed, 08 Apr 2009 09:36:13 -0400
> 
> I was just navigating my way back to a point in the Emacs Manual, the
> section, `22 File Handling'.  I did `t', `m' and then typed
> 
> file h <TAB>
> 
> ``[No Match]'' was the message that I got.
> 
> From the top level of the manual, ``Files'' is the name of the section.
> I remembered the last chapter name or section name I'd come across
> (again, `22 File Handling') as I do when I close a book and put it down.

In an Info manual, there are node names and there are section names.
A section name is what you see at the beginning of the section;
"22 File Handling" is an example.  The corresponding node name appears
in the mode line, where you should see "(emacs) Files", which tells
you that you are in the node "Files" of the "emacs" manual.

The `m' command wants a node name, not the name of a section.  More
accurately, it wants the name of a menu item.  Normally, menu items
are just node names, but sometimes they also have an additional menu
entry name.  Here are two examples:

     * Files::                       All about handling files.
     * Multiples: Buffers.           Multiple buffers; editing
                                      several files at once.

The reason the `m' command does not work on section names is because
it looks at the menu entries, not at the list of all the sections in
the manual.  And section names do not appear in the menu entries.




  reply	other threads:[~2009-04-08 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 13:36 emacs manual Sean Sieger
2009-04-08 14:35 ` Eli Zaretskii [this message]
2009-04-10 14:07   ` Sean Sieger
2009-04-08 14:37 ` tyler

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=83vdpf43iz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.