From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27277@debbugs.gnu.org
Subject: bug#27277: 25.2; Be able to get back to the *Help* of query-replace
Date: Sun, 21 Jul 2019 14:10:47 -0700 (PDT) [thread overview]
Message-ID: <8ae1efe0-fcf3-442b-a371-c42a50ff8556@default> (raw)
In-Reply-To: <8736iz46yx.fsf@mouse.gnus.org>
> > 1. Use `M-%' to do some query-replacing. Hit `?' during
> > query-replacing, to see the query-replace help, in buffer *Help*.
> >
> > 2. Use a help command, such as `C-h f'. The contents of *Help* do
> not
> > show a Back button, to get to the query-replace help. They should.
>
> I don't agree -- that seems like such a context-dependent help buffer
> that it's not very helpful to include that in the stack of help
> buffers. Other help buffers usually have links to things you can jump
> to and the like. Closing.
No. Forward links from *Help* to, say,
function-name *Help* display could be
considered to be for related information.
The [back] link is explicitly NOT that.
It's purely a chronological link, to take you
back to the _previously shown_ *Help* content,
whatever that might be. Similarly, for
[forward].
`C-h f completing-read' followed by `C-h v
fill-column' has nothing to do with related
information. [back] just goes back in time.
You've apparently misunderstood what [back]
and the help-stack is for.
If we wanted only links to related information,
and no chronological backtracking links, then
we would not have the stack - no [back] and
[forward]. (That's what we had in the old days.)
The [back] and [forward] links in *Help* are,
like `l' and `r' in Info, and like the Back and
Forward links in your browser, purely chronological.
Info has Up, Next, and Previous links for
structural navigation. And it has inline (See)
links for related information. Such things are
not to be confused with chronological-visit
links.
Please consider reopening this bug. Thx.
prev parent reply other threads:[~2019-07-21 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 17:03 bug#27277: 25.2; Be able to get back to the *Help* of query-replace Drew Adams
2019-07-21 17:45 ` Lars Ingebrigtsen
2019-07-21 21:10 ` Drew Adams [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=8ae1efe0-fcf3-442b-a371-c42a50ff8556@default \
--to=drew.adams@oracle.com \
--cc=27277@debbugs.gnu.org \
--cc=larsi@gnus.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).