unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: info
Date: Fri, 31 Jan 2003 13:05:18 +0000 (UTC)	[thread overview]
Message-ID: <m18ear8-000IeAC@localhost> (raw)
In-Reply-To: <200301310151.TAA10405@eel.dms.auburn.edu> (message from Luc Teirlinck on Thu, 30 Jan 2003 19:51:59 -0600 (CST))

Today's CVS snapshot, Fri, 2003 Jan 31  12:37 UTC
GNU Emacs 21.3.50.113 (i686-pc-linux-gnu, X toolkit)
started with

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

I wrote:

          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

  Luc Teirlinck <teirllm@dms.auburn.edu> responded

       It visits the Info file if you are on the actual *-line.

No, it does not do that in my dir file, but it does visit the proper
node when within a manual.  I do not know why this is.  This is with a
plain vanilla Emacs: no .emacs file, no site file.

When dir is

  /usr/local/info/dir

and point is just before the `r' of `format', in the menu line that
says:

* Texinfo: (texinfo).				The GNU documentation format.

when I press RET (Info-follow-nearest-node), I receive the error message:

    Info-next-preorder: No more nodes

However, when point is just before the `x' of `Texinfo', 
when I press RET, I visit the Texinfo manual.  

Within that manual, regardless of where point is on a *-line, RET
(Info-follow-nearest-node) sends me to the node for that line.

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

  reply	other threads:[~2003-01-31 13:05 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           ` info Robert J. Chassell
2003-01-31  1:51             ` info Luc Teirlinck
2003-01-31 13:05               ` Robert J. Chassell [this message]
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

  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=m18ear8-000IeAC@localhost \
    --to=bob@rattlesnake.com \
    --cc=bob@gnu.org \
    --cc=emacs-devel@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).