From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9528@debbugs.gnu.org
Subject: bug#9528: 24.0.50; Info navigation
Date: Mon, 19 Sep 2011 08:49:38 -0400 [thread overview]
Message-ID: <E1R5dI2-0001h3-9D@fencepost.gnu.org> (raw)
In-Reply-To: <CAH8Pv0gbTQKT4AFHPLGUNA-cX7HZ5t=oRf3xM28ZtceiEUyDfg@mail.gmail.com> (message from Dani Moncayo on Mon, 19 Sep 2011 14:14:26 +0200)
> Date: Mon, 19 Sep 2011 14:14:26 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: juri@jurta.org, 9528@debbugs.gnu.org
>
> >> > It's not the implementation, it's part of documented behavior of DEL:
> >> >
> >> > Scroll one screenful back in Info, considering all nodes as one
> >> > sequence ----------------------------
> >> > --------
> >>
> >> As I see it, considering all nodes as one sequence, the node just
> >> before "Macros" is "Related Topics", not "Functions".
> >
> > Not in depth-first-search order, it isn't.
>
> In that order maybe not, but I think the intended order is not that,
> but "sequential", as described in (info "(info)Help-^L"):
An Info manual has a tree structure, so sequential order is not well
defined. If you read the description in Help-^L, you will see that it
describes depth-first-search:
In this sequence, a node's subnodes appear following their parent.
If a node has a menu, <SPC> takes you into the subnodes listed in the
menu, one by one. Once you reach the end of a node, and have seen all
of its subnodes, <SPC> takes you to the next node or to the parent's
next node.
next prev parent reply other threads:[~2011-09-19 12:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 10:54 bug#9528: 24.0.50; Info navigation Dani Moncayo
2011-09-17 11:01 ` Dani Moncayo
2011-09-17 18:02 ` Juri Linkov
2011-09-17 18:00 ` Juri Linkov
2011-09-18 20:14 ` Juri Linkov
2011-09-19 8:14 ` Dani Moncayo
2011-09-19 9:49 ` Eli Zaretskii
2011-09-19 10:20 ` Dani Moncayo
2011-09-19 10:37 ` Eli Zaretskii
2011-09-19 10:49 ` Dani Moncayo
2011-09-19 11:24 ` Eli Zaretskii
2011-09-19 12:14 ` Dani Moncayo
2011-09-19 12:49 ` Eli Zaretskii [this message]
2011-09-19 13:04 ` Dani Moncayo
2011-09-19 14:24 ` Stefan Monnier
2011-09-19 16:03 ` Eli Zaretskii
2011-09-19 16:41 ` Stefan Monnier
2011-09-19 16:52 ` Eli Zaretskii
2011-09-19 18:49 ` Juri Linkov
2011-09-19 19:57 ` Eli Zaretskii
2011-09-20 16:30 ` Juri Linkov
2011-09-20 17:30 ` Eli Zaretskii
2011-09-20 17:50 ` Juri Linkov
2011-09-20 19:24 ` Eli Zaretskii
2011-09-20 20:17 ` Juri Linkov
2011-09-19 11:16 ` Juri Linkov
2011-09-19 11:25 ` Eli Zaretskii
2011-09-19 12:45 ` Dani Moncayo
2011-09-19 14:23 ` Juri Linkov
2011-09-19 16:06 ` Eli Zaretskii
2011-09-20 16:28 ` Juri Linkov
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=E1R5dI2-0001h3-9D@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9528@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
/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).