From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: info
Date: Thu, 30 Jan 2003 19:51:59 -0600 (CST) [thread overview]
Message-ID: <200301310151.TAA10405@eel.dms.auburn.edu> (raw)
In-Reply-To: <m18eNJh-000IeGC@localhost> (bob@rattlesnake.com)
Robert Chassell 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
It visits the Info file if you are on the actual *-line. Otherwise a
variety of things can happen, depending on the situation.
For instance:
* Emacs Lisp Intro: (eintr).
A simple introduction to Emacs Lisp programming.
* Eshell: (eshell). A command shell implemented in Emacs Lisp.
Note: (eintr) and (eshell) only became visible after yanking.
If I press RETURN on "A simple ...", I would be visiting the Eshell
file, because I am not on the *-line. If Emacs Lisp Intro: were
the last node, I would be getting the error message you got.
Positioning point above the `A" goes to `File: eintr'. We see:
* Narrowing & Widening:: Restricting your and Emacs attention to
a region.
* car cdr & cons:: Fundamental functions in Lisp.
RETURN on "Restricting ..." goes to "Narrowing & Widening::"
RETURN on "a region." goes to "car cdr & cons::"
We all agree that the behavior on the *-line is correct and the
behavior on the next line wrong. What we are discussing is what the
behavior on other lines should be. At first it looks obvious: we want
exactly the same behavior as on the *-line in both cases since we are
on a continuation line. (That is exactly what I originally proposed.)
But somehow things are not that straightforward, for reasons discussed
earlier in this thread.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-01-31 1:51 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 ` Luc Teirlinck [this message]
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=200301310151.TAA10405@eel.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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 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.