From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: help-go-back
Date: Sun, 09 May 2004 03:08:09 +0300 [thread overview]
Message-ID: <87fzaajwd2.fsf@mail.jurta.org> (raw)
In-Reply-To: <quack.20040508T1524.j5ekpueewr@hkn.eecs.berkeley.edu> (Karl Chen's message of "Sat, 08 May 2004 15:24:04 -0700")
Karl Chen <quarl+dated+1084486903.a9a7a9@nospam.quarl.org> writes:
>>>>>> "Juri" == Juri Linkov <juri@jurta.org> writes:
> >> It would also be nice if there were a `help-go-forward'
> >> (opposite of `help-go-back'). I can write this if there is
> >> interest.
> Juri> It is not possible to implement it with the current
> Juri> `help-xref-stack' variable. A new variable could be
> Juri> added that will record the full Help history. And it
> Juri> might be as useful as full history of Info nodes where
> Juri> an additional variable with full history was added
> Juri> recently.
>
> I was thinking a list of nodes to go forward to (reverse of the
> 'back' stack). I'm not sure what you mean re. Info nodes, do you
> want to combine the two histories?
No, I meant not to combine, but to implement the full Help history list
similar to full Info history list recently implemented, i.e. a list
of all visited Help elements which is displayed in the Help buffer by
a special command, and where older help elements could be revisited by
selecting an element from the full history list.
However, AFAIU, you propose a stack of forward elements, which is
filled by `help-xref-go-back', used by a new `help-xref-go-forward'
command and cleared after the first visit of some other cross-reference.
This may be useful as well, although generally this is a subset of
the full history list.
BTW, since you misunderstood me in such a way that I proposed to
combine the Info and Help histories, it seems it was not accidentally,
because more close integration of Help with Info seems very natural.
Many improvements could be done here. At least, the Help buffer could
provide automatic buttons with links to Info manuals and call
something like `info-lookup-symbol' or `Info-goto-emacs-command-node'.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-05-09 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 20:44 help-go-back Karl Chen
2004-05-08 21:32 ` help-go-back Juri Linkov
2004-05-08 22:24 ` help-go-back Karl Chen
2004-05-09 0:08 ` Juri Linkov [this message]
2004-05-09 0:48 ` help-go-back Nick Roberts
2004-05-09 1:11 ` help-go-back Juri Linkov
2004-05-09 6:52 ` help-go-back Eli Zaretskii
2004-05-09 11:25 ` help-go-back Juri Linkov
2004-05-09 18:47 ` help-go-back Richard Stallman
2004-05-19 0:57 ` help-go-back Stefan Monnier
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=87fzaajwd2.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@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).