From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 4979@emacsbugs.donarmstrong.com
Subject: bug#4979: 23.1.50; describe-text-properties produces *Help* buffer without back/forward buttons
Date: Wed, 25 Nov 2009 23:35:43 +0100 [thread overview]
Message-ID: <954F1651-3C33-46D4-88DF-485825734F30@Freenet.DE> (raw)
In-Reply-To: <jwvaaybimti.fsf-monnier+emacsbugreports@gnu.org>
Am 24.11.2009 um 23:24 schrieb Stefan Monnier:
>> 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
The functions describe-minor-mode-from-indicator and describe-minor-
mode do not show any possible completions...
--
Greetings
Pete <\
_\ O _
|o \ _\\_/-\='
_____________(_)|-(_) (_)___________________________________
next prev parent reply other threads:[~2009-11-25 22:35 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 [this message]
2021-07-18 18:48 ` Lars Ingebrigtsen
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=954F1651-3C33-46D4-88DF-485825734F30@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=4979@emacsbugs.donarmstrong.com \
--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).