all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9528@debbugs.gnu.org
Subject: bug#9528: 24.0.50; Info navigation
Date: Sun, 18 Sep 2011 23:14:52 +0300	[thread overview]
Message-ID: <87mxe1li9l.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0j8Aj885hEFn_rWdqf3vEeHE6CRyyoTAeLWBPY0Hnt2Hw@mail.gmail.com> (Dani Moncayo's message of "Sat, 17 Sep 2011 12:54:50 +0200")

> I noticed several malfunctions in info navigation commands.
>
> The following recipes start from "emacs -Q":
>
> ------------------------------------------------
> 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.

> ------------------------------------------------
> 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.

> ------------------------------------------------
> 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.

> ------------------------------------------------
>
> Note: The behavior I expect is based on what I've read in info-mode
> help (C-h i ?).





  parent reply	other threads:[~2011-09-18 20: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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mxe1li9l.fsf@mail.jurta.org \
    --to=juri@jurta.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 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.