From: Akib Azmain Turja via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ikumi Keita <ikumi@ikumi.que.jp>, 60006@debbugs.gnu.org
Subject: bug#60006: 28.2; C-h f reports wrong version
Date: Mon, 12 Dec 2022 22:16:59 +0600 [thread overview]
Message-ID: <87edt47g1w.fsf@disroot.org> (raw)
In-Reply-To: <83zgbsr736.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Dec 2022 17:10:21 +0200")
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Ikumi Keita <ikumi@ikumi.que.jp>
>> Date: Mon, 12 Dec 2022 22:42:32 +0900
>>
>> C-h f reports wrong version when `always' was introduced.
>>
>> [How to reproduce]
>> 1. emacs-28.2 -Q
>> 2. Type C-h f always RET
>> 3. Then *Help* buffer says:
>> Probably introduced at or before Emacs version 1.1.
For me, it is: "Probably introduced at or before Emacs version 25.1."
>
> That's why it says "Probably". The method of finding out the first
> release where the symbol appeared is a heuristic, and it can sometimes
> fail in ridiculous ways.
Just out of curiosity, what heuristic exactly?
--
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-12-12 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 13:42 bug#60006: 28.2; C-h f reports wrong version Ikumi Keita
2022-12-12 15:10 ` Eli Zaretskii
2022-12-12 16:16 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-12 20:26 ` Eli Zaretskii
2022-12-13 0:48 ` Stefan Kangas
2022-12-13 3:37 ` Eli Zaretskii
2022-12-13 5:05 ` Ikumi Keita
2022-12-13 6:46 ` Stefan Kangas
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=87edt47g1w.fsf@disroot.org \
--to=bug-gnu-emacs@gnu.org \
--cc=60006@debbugs.gnu.org \
--cc=akib@disroot.org \
--cc=eliz@gnu.org \
--cc=ikumi@ikumi.que.jp \
/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.