From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 72554@debbugs.gnu.org
Subject: bug#72554: 31.0.50; misleading release information for 'always'
Date: Sat, 10 Aug 2024 14:42:04 +0300 [thread overview]
Message-ID: <86frrck3jn.fsf@gnu.org> (raw)
In-Reply-To: <u1q2waar0@gentoo.org> (message from Ulrich Mueller on Sat, 10 Aug 2024 13:16:35 +0200)
> From: Ulrich Mueller <ulm@gentoo.org>
> Date: Sat, 10 Aug 2024 13:16:35 +0200
>
> "C-h f always RET" says:
>
> always is a byte-compiled Lisp function in ‘subr.el’.
> [...]
>
> Probably introduced at or before Emacs version 25.1.
> This function does not change global state, including the match data.
>
> However, 'always' only appeared in Emacs 28, so that information is
> misleading when trying to write backwards compatible code.
>
> (It's less of a problem when the version that is shown is greater than
> the actual first release, which I think happens more often.)
>
> Not sure how to fix this. Maybe exclude common English words (which
> are likely to appear in NEWS* without being the name of a function)
> from scanning in help-fns.el?
help-fns--first-release-regexp is supposed to find only quoted names,
so the problem is not with common words. I think it finds this in
NEWS.25:
*** New value 'always' for 'sh-indent-after-continuation'.
^^^^^^^^
So maybe we should reject matches that immediately follow "value" or
"values". That won't reject all false positives, but it should be an
improvement, I think.
next prev parent reply other threads:[~2024-08-10 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 11:16 bug#72554: 31.0.50; misleading release information for 'always' Ulrich Mueller
2024-08-10 11:42 ` Eli Zaretskii [this message]
2024-08-10 12:07 ` Ulrich Mueller
2024-08-10 12:47 ` Eli Zaretskii
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=86frrck3jn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72554@debbugs.gnu.org \
--cc=ulm@gentoo.org \
/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.