From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Wrong minimum emacs version in flymake.el
Date: Thu, 09 Dec 2021 17:02:51 +0200 [thread overview]
Message-ID: <83lf0tu8h0.fsf@gnu.org> (raw)
In-Reply-To: <CAEpr+AVoTpZBsXBUjqKoDrwTt5UcmjGRBw_+dxDMa6J6syQ29A@mail.gmail.com> (message from Guillaume Pasquet on Thu, 9 Dec 2021 14:21:50 +0000)
> From: Guillaume Pasquet <guillaume@bitimplosion.com>
> Date: Thu, 9 Dec 2021 14:21:50 +0000
>
> I've notice that flymake.el in master states that it requires minimum emacs
> 26.1, however this doesn't seem to be true as it makes use of the
> `string-replace` function, which was introduced in Emacs 28 AFAIK.
>
> Please either update the minimum emacs requirement for flymake or
> substitute the `string-replace` call with `replace-regexp-in-string` to
> maintain compatibility as I have done here:
Done, thanks.
prev parent reply other threads:[~2021-12-09 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 14:21 Wrong minimum emacs version in flymake.el Guillaume Pasquet
2021-12-09 14:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-09 15:02 ` 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=83lf0tu8h0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).