From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9528@debbugs.gnu.org
Subject: bug#9528: 24.0.50; Info navigation
Date: Mon, 19 Sep 2011 12:49:09 +0200 [thread overview]
Message-ID: <CAH8Pv0hiyJ-x9J4NQNOkPAFFum-JXBEfQ2f_qjrt-G4k3_7dCw@mail.gmail.com> (raw)
In-Reply-To: <E1R5bDi-0004Xf-7n@fencepost.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". IOW, <DEL>
should show the nodes in the same sequential order that appear in the
printed version of the manual, and likewise for <SPC>.
Then `l' should jump back to previously visited (well, presented to
the user) nodes.
--
Dani Moncayo
next prev parent reply other threads:[~2011-09-19 10: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 [this message]
2011-09-19 11:24 ` Eli Zaretskii
2011-09-19 12:14 ` Dani Moncayo
2011-09-19 12:49 ` Eli Zaretskii
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=CAH8Pv0hiyJ-x9J4NQNOkPAFFum-JXBEfQ2f_qjrt-G4k3_7dCw@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=9528@debbugs.gnu.org \
--cc=eliz@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).