From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 9528@debbugs.gnu.org
Subject: bug#9528: 24.0.50; Info navigation
Date: Mon, 19 Sep 2011 10:14:24 +0200 [thread overview]
Message-ID: <CAH8Pv0i=NA5HmO+_4-iFvs9rSyQBDv_d5hrsgrOL1_v6JKPXyQ@mail.gmail.com> (raw)
In-Reply-To: <87mxe1li9l.fsf@mail.jurta.org>
>> ------------------------------------------------
>> 1. Eval: (info "(elisp)Macros")
>> 2. Type: <DEL>
>> --> Go to node "(elisp)Related Topics" (OK).
>> 3. Type: l
>> --> (Expected) Go to the last-visited info node (i.e., "(elisp)Macros").
>> --> (Observed) Go to node "(elisp)Functions".
>
> Fixed the same way as bug#208.
Tested. Thanks.
>> ------------------------------------------------
>> 1. Eval: (info "(elisp)Macros")
>> 2. Move point to line 21 (* Menu:).
>> 3. Type: <DEL>
>> --> (Expected) Go to node "(elisp)Related Topics".
>> --> (Observed) Go to node "(elisp)Process Internals".
>
> Fixed this bug as well.
Tested. Thanks.
>> ------------------------------------------------
>> 1. Eval: (info "(elisp)Macros")
>> 2. Move point to line 22 (* Simple Macro).
>> 3. Type: <DEL>
>> --> (Expected) Go to node "(elisp)Related Topics".
>> --> (Observed) Go to node "(elisp)Simple Macro".
>
> Sorry, I can't change this because this behavior is explicitly
> implemented in Info, so it's not a bug.
Then I have a couple of things to say about this:
* The current behavior is not documented AFAIK [1].
* Even if the behavior was documented, it is not desirable (IMO),
because we already have a specific command to follow a
cross-reference: <RET>. Thus, if I type <DEL> in an info buffer, I'd
like to see the same behavior (going back) regardless of whether the
point is on a cross-reference or not. It is much clearer to keep
these behaviors separated.
>>> 2. Move point to line 22 (* Simple Macro).
>>
>> Actually, that line is the 23rd. Sorry.
>
> BTW, `M-g g' (`goto-line') doesn't work in Info.
> Should be fixed too.
Of course I agree. `goto-line' should be consistent with the line
numbers showed in the modeline, regardless of whether the buffer is
narrowed or not. The current behavior is confusing for users, I
think.
Footnotes:
[1] The info mode help (C-h i ?) says this about <DEL>: "Normally,
scroll backward. If the beginning of the buffer is already visible,
try to go to the previous menu entry, or up if the is none.".
--
Dani Moncayo
next prev parent reply other threads:[~2011-09-19 8:14 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 [this message]
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
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='CAH8Pv0i=NA5HmO+_4-iFvs9rSyQBDv_d5hrsgrOL1_v6JKPXyQ@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=9528@debbugs.gnu.org \
--cc=juri@jurta.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).