all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: philip-agee@africamel.net
Cc: 49166@debbugs.gnu.org
Subject: bug#49166: Writing in help-buffer does not show in history
Date: Tue, 22 Jun 2021 15:30:06 +0200	[thread overview]
Message-ID: <87zgviowm9.fsf@gnus.org> (raw)
In-Reply-To: <ea-mime-60d10838-38d-3f6e66d3@www-7.mailo.com> (philip-agee@africamel.net's message of "Mon, 21 Jun 2021 23:44:24 +0200 (CEST)")

philip-agee@africamel.net writes:

> Have written the following function that inserts text in the
> help-buffer.
>
> Was curious to see whether the inserted text persist if one uses
> the buttons or commands in the Help Buffer that take you
> back/forth in the history of visited entries (you can invoke
> those commands with 'l' for left ('help-go-back') and 'r' for
> right ('help-go-forward')).
>
> It does not show in the history when using ('help-go-back').
>
> Does it make sense to include the text in the history?

The *Help* history doesn't save the actual text in the buffer, but
regenerates it based on the parameters given -- so if you go back to the
documentation for, say `describe-mode', it'll regenerate the buffer
based on the current documentation for that command.  This also means
that if you change the documentation (loading a new version, for
instance), you'll get the new version of the doc string, and not the old
one.

So this is working as intended, and I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2021-06-22 13:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 21:44 bug#49166: Writing in help-buffer does not show in history philip-agee
2021-06-22  9:34 ` Basil L. Contovounesios
2021-06-22 13:30 ` Lars Ingebrigtsen [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

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

  git send-email \
    --in-reply-to=87zgviowm9.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=49166@debbugs.gnu.org \
    --cc=philip-agee@africamel.net \
    /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.