all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: info
Date: Thu, 30 Jan 2003 22:37:53 +0000 (UTC)	[thread overview]
Message-ID: <m18eNJh-000IeGC@localhost> (raw)
In-Reply-To: <9743-Thu30Jan2003220221+0200-eliz@is.elta.co.il>

Today's CVS snapshot, Thu, 2003 Jan 30  22:22 UTC,
GNU Emacs 21.3.50.112 (i686-pc-linux-gnu, X toolkit)
started with

     /usr/local/bin/emacs -q --no-site-file --eval '(blink-cursor-mode 0)'

   > First of all, if point is on a menu line, then choose that menu
   > item.  That much we all agree on.

   Doesn't Emacs do that now?  I thought it did.

No, it does not -- not in the Dir file.   This is one of the problems.

In the Dir file, when point is in a description, and you press RET,
Emacs does not visit the Info file, but returns an error message that
says:

    Info-next-preorder: No more nodes

(The command that RET invokes is `Info-follow-nearest-node'.)

However, when point is at the beginning of a menu line (just before
the asterisk) or when point is within the name of the menu item, and
you press RET, then Emacs does visit the Info file.

On the other hand, within a document, whenever point is anywhere on a
menu entry line, even when it is a description, then when you press
RET, Emacs visits the appropriate node.

-- 
    Robert J. Chassell                         Rattlesnake Enterprises
    http://www.rattlesnake.com                  GnuPG Key ID: 004B4AC8
    http://www.teak.cc                                     bob@gnu.org

  parent reply	other threads:[~2003-01-30 22:37 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  1:33 info Luc Teirlinck
2003-01-29  3:53 ` info Luc Teirlinck
2003-01-29  6:29   ` info Eli Zaretskii
2003-01-29 19:57     ` info Luc Teirlinck
2003-01-30  5:46       ` info Eli Zaretskii
2003-01-29 21:17   ` info Richard Stallman
2003-01-29 17:33 ` info Eli Zaretskii
2003-01-29 20:39   ` info Luc Teirlinck
2003-01-29 23:21     ` info Luc Teirlinck
2003-01-30  5:48     ` info Eli Zaretskii
2003-01-30  8:39       ` info Kai Großjohann
2003-01-30 15:11         ` info Luc Teirlinck
2003-01-30 16:30           ` info Luc Teirlinck
2003-01-30 20:02         ` info Eli Zaretskii
2003-01-30 20:51           ` info Kai Großjohann
2003-01-30 22:37           ` Robert J. Chassell [this message]
2003-01-31  1:51             ` info Luc Teirlinck
2003-01-31 13:05               ` info Robert J. Chassell
2003-01-31 20:22                 ` info Luc Teirlinck
2003-02-01  1:22                   ` info Robert J. Chassell
2003-01-29 21:17 ` info Richard Stallman
2003-01-30  0:31   ` info Luc Teirlinck
2003-01-30  1:43     ` info Luc Teirlinck
2003-01-30  2:03       ` info Luc Teirlinck
     [not found] <84smvc2guf.fsf@lucy.is.informatik.uni-duisburg.de>
2003-01-29 14:20 ` info Eli Zaretskii
2003-01-30 15:21   ` info Richard Stallman
2003-01-30 16:21     ` info Luc Teirlinck
2003-01-31 19:20       ` info Richard Stallman
2003-02-01  1:22         ` info Luc Teirlinck
2003-02-01 22:11           ` info Richard Stallman
2003-02-02  4:59             ` info Luc Teirlinck
2003-02-02  5:44             ` info Eli Zaretskii
2003-02-02  6:09               ` info Miles Bader
2003-02-03 14:40             ` info Stefan Monnier
2003-02-03 19:00               ` info Luc Teirlinck
2003-02-03 19:16                 ` info Luc Teirlinck
2003-02-03 19:19                   ` info Luc Teirlinck
2003-02-04 15:41                 ` info Richard Stallman
2003-02-05  6:08                   ` info Eli Zaretskii
2003-02-05 20:07                     ` info Luc Teirlinck
2003-02-09  4:45                       ` info Luc Teirlinck

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=m18eNJh-000IeGC@localhost \
    --to=bob@rattlesnake.com \
    --cc=bob@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.