unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: 9528@debbugs.gnu.org
Subject: bug#9528: 24.0.50; Info navigation
Date: Tue, 20 Sep 2011 20:30:06 +0300	[thread overview]
Message-ID: <83y5xjrujl.fsf@gnu.org> (raw)
In-Reply-To: <87hb47migm.fsf@mail.jurta.org>

> From: Juri Linkov <juri@jurta.org>
> Cc: monnier@iro.umontreal.ca,  9528@debbugs.gnu.org
> Date: Tue, 20 Sep 2011 19:30:01 +0300
> 
> 1. Run `emacs -Q'
> 2. `C-h i m elisp RET g Macros RET'
> 3. `[' (`Info-backward-node') goes to "Related Topics".
> 4. `l' goes back to the previously selected node "Macros".
> 
> 1. Run `info'
> 2. `m elisp RET g Macros RET'
> 3. `[' (`Info-backward-node') goes to "Related Topics".
> 4. `l' goes to the node "Functions", not "Macros".
> 
> The behavior of the Emacs Info reader to skip intermediate nodes by default
> dates back to the first version of info.el at 1991-07-13.

You mean, when `[' is used?  Because otherwise, the Emacs behavior
with `l' was like the stand-alone Info, until you changed that a day
or two ago, right?

> If you think that behavior of the stand-alone Info reader
> is more traditional, we could install this patch:

Yes, assuming I understand correctly what you are saying, see above.





  reply	other threads:[~2011-09-20 17:30 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
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 [this message]
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=83y5xjrujl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).