From: Lars Ingebrigtsen <larsi@gnus.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, 4979@debbugs.gnu.org
Subject: bug#4979: 23.1.50; describe-text-properties produces *Help* buffer without back/forward buttons
Date: Sun, 18 Jul 2021 20:48:04 +0200 [thread overview]
Message-ID: <87k0lno3vf.fsf@gnus.org> (raw)
In-Reply-To: <954F1651-3C33-46D4-88DF-485825734F30@Freenet.DE> (Peter Dyballa's message of "Wed, 25 Nov 2009 23:35:43 +0100")
Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:
>>> Shouldn't all functions which overwrite the previous contents of
>>> *Help*
>>> buffer also insert that [back] button?
>>
>> Yes. I've installed a change which should fix it for
>> describe-text-properties and describe-char. Please confirm that it
>> solves your problems,
>
> Yes, I can confirm that describe-text-properties now works as
> describe-function or describe-variable.
>
> But – there seem to be other describe-<whatever> functions which do
> not work like these. Some of these functions produce a [back] key only
> when they are repeated (describe-character-set for example,
> describe-categories, describe-face, describe-fontset) and not when
> they overwrite the contents of the *Help* buffer. Some never seem to
> create this navigation element:
>
> describe-bindings-internal
> describe-buffer-case-table
> describe-coding-system
> describe-current-coding-system
> describe-current-display-table
> describe-font
I tried the commands here in Emacs 28, and they all seemed to produce a
[back] button for me, so I'm going to go ahead and guess that this has
been fixed in the decade since it was reported, and I'm closing this bug
report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-07-18 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 21:23 bug#4979: 23.1.50; describe-text-properties produces *Help* buffer without back/forward buttons Peter Dyballa
2009-11-24 22:24 ` Stefan Monnier
2009-11-25 22:35 ` Peter Dyballa
2021-07-18 18:48 ` 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
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=87k0lno3vf.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=4979@debbugs.gnu.org \
--cc=Peter_Dyballa@Freenet.DE \
--cc=monnier@IRO.UMontreal.CA \
/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).