From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; `l' in Info skips last visited node
Date: Sun, 11 May 2008 03:08:55 +0300 [thread overview]
Message-ID: <87r6c9hfc8.fsf@jurta.org> (raw)
In-Reply-To: <87prrv6n6w.fsf@jurta.org> (Juri Linkov's message of "Sat, 10 May 2008 02:57:31 +0300")
>> C-h i, choose Elisp manual.
>> g Customization Types
>> m d TAB RET, to go to node Defining New Types
>> SPC SPC to get to node Loading
>> l
>>
>> This takes you back to node Customization, not to the last visited
>> node, which is Defining New Types, or even to the node visited just
>> before that, which is Customization Types. Node Customization is the
>> grandparent of the last visited node, and it was never even visited.
>
> This is confusing but deliberate. I agree we should change it.
This can be fixed with the following patch:
Index: lisp/info.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/info.el,v
retrieving revision 1.531
diff -c -r1.531 info.el
*** lisp/info.el 6 May 2008 07:57:40 -0000 1.531
--- lisp/info.el 11 May 2008 00:07:47 -0000
***************
*** 2526,2533 ****
;; go up to the end of this node.
(goto-char (point-max))
;; Since logically we are done with the node with that menu,
! ;; move on from it.
! (Info-next-preorder))
(t
(error "No more nodes"))))
--- 2526,2535 ----
;; go up to the end of this node.
(goto-char (point-max))
;; Since logically we are done with the node with that menu,
! ;; move on from it. But don't put intermediate nodes to the
! ;; history on recursive calls.
! (let (Info-history)
! (Info-next-preorder)))
(t
(error "No more nodes"))))
--
Juri Linkov
http://www.jurta.org/emacs/
prev parent reply other threads:[~2008-05-11 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 15:44 23.0.60; `l' in Info skips last visited node Drew Adams
2008-05-09 23:57 ` Juri Linkov
2008-05-11 0:08 ` Juri Linkov [this message]
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=87r6c9hfc8.fsf@jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@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).