From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 65288@debbugs.gnu.org
Subject: bug#65288: 30.0.93; Add a NEWS entry for `help-display-function-type'
Date: Tue, 07 Jan 2025 20:24:59 +0200 [thread overview]
Message-ID: <86frlu4h38.fsf@gnu.org> (raw)
In-Reply-To: <9c1d0b59578347b82ef93612eaa9eb06@webmail.orcon.net.nz> (message from Phil Sainty on Wed, 08 Jan 2025 00:49:07 +1300)
> Date: Wed, 08 Jan 2025 00:49:07 +1300
> From: Phil Sainty <psainty@orcon.net.nz>
>
> The new user option `help-display-function-type' enables the
> "Inferred type" and "Declared type" specs to be hidden, but
> I think it needs a NEWS item.
>
> With the type information displayed so prominently and frequently,
> I'm sure that a lot of users will be searching NEWS for the text
> "Inferred type" and/or "Declared type" to find out why they've
> started appearing; what they mean; and quite likely how to get
> rid of them.
These terms did already appear in NEWS and in the manuals. I added
the variable there, so I think we are good now.
Thanks.
prev parent reply other threads:[~2025-01-07 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 12:29 bug#65288: 30.0.50; Make Type: annotation optional in *Help* buffers Visuwesh
2023-08-14 13:51 ` Philip Kaludercic
2023-08-14 14:25 ` Helmut Eller
2023-08-14 14:44 ` Philip Kaludercic
2023-08-14 15:13 ` Helmut Eller
2023-08-14 16:03 ` Philip Kaludercic
2023-08-14 17:11 ` Helmut Eller
2023-08-14 15:17 ` Visuwesh
2023-08-19 8:28 ` Eli Zaretskii
2023-08-19 9:53 ` Gregory Heytings
2023-08-20 10:11 ` Andrea Corallo
[not found] ` <CA38BAAD-3FC3-4345-8F86-47E61AD4A92F@posteo.net>
2023-08-20 10:24 ` Andrea Corallo
2023-08-20 12:19 ` Philip Kaludercic
2023-08-20 10:37 ` Eli Zaretskii
2023-08-20 20:39 ` Andrea Corallo
2023-08-21 12:15 ` Eli Zaretskii
2025-01-07 11:49 ` bug#65288: 30.0.93; Add a NEWS entry for `help-display-function-type' Phil Sainty
2025-01-07 18:24 ` Eli Zaretskii [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=86frlu4h38.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65288@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/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).