unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Brian Leung <leungbk@posteo.net>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	53853@debbugs.gnu.org
Subject: bug#53853: [PATCH] Don't use string-replace in flymake
Date: Tue, 8 Feb 2022 09:52:34 +0000	[thread overview]
Message-ID: <CALDnm537vn56-gmKFxOr3pZ1VyVhx6Xd+koj=qU-uaUKqyyg1w@mail.gmail.com> (raw)
In-Reply-To: <87mtj17oqg.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On Tue, Feb 8, 2022 at 9:26 AM Robert Pluim <rpluim@gmail.com> wrote:

> >>>>> On Tue, 08 Feb 2022 07:16:40 +0100, Lars Ingebrigtsen <
> larsi@gnus.org> said:
>
>     Lars> Brian Leung <leungbk@posteo.net> writes:
>     >> OK, I've updated the patch per your suggestions. I've also made the
>     >> commit apply to the emacs-28 branch, as opposed to the master
> branch.
>
>     Lars> Thanks; pushed to emacs-28.
>
> Iʼm not au fait with how core packages work, does this require a bump
> in flymake's package version?


Yes, Robert, I believe so. Else the core package won't get regenerated into
GNU ELPA.

What _doesn't_ require a bump is, for example, `eglot.el` usage of it.  So
if you
bump flymake.el to, say, 1.9 now and eglot.el is still asking for 1.8, I
think package.el
will pull in the latest one regardless and the problem for eglot.el users
will be fixed.

I suspect though, that this problem only happened because the user was using
the straight.el package manager, which will try to fetch the very latest
(i.e.
not go through GNU ELPA as package.el does).

Anyway, thanks for fixing this.
João

[-- Attachment #2: Type: text/html, Size: 1749 bytes --]

  parent reply	other threads:[~2022-02-08  9:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 16:11 bug#53853: [PATCH] Don't use string-replace in flymake Brian Leung
2022-02-07 17:32 ` Robert Pluim
2022-02-08  2:17   ` Brian Leung
2022-02-08  6:16     ` Lars Ingebrigtsen
2022-02-08  8:21       ` Robert Pluim
2022-02-08  8:28         ` Brian Leung
2022-02-08  8:35           ` Robert Pluim
2022-02-08  9:20             ` João Távora
2022-02-08  9:50               ` Robert Pluim
2022-02-08  9:54                 ` João Távora
2022-02-08  9:58                   ` João Távora
2022-02-08 13:03                     ` Eli Zaretskii
2022-02-08 13:18                       ` João Távora
2022-02-08 13:54                         ` Eli Zaretskii
2022-02-08 14:09                           ` João Távora
2022-02-08 15:07                             ` Robert Pluim
2022-02-08 15:30                               ` João Távora
2022-02-08 15:47                                 ` Robert Pluim
2022-02-08 15:51                                   ` João Távora
2022-02-08 16:02                                     ` Robert Pluim
2022-02-08 16:43                                       ` João Távora
2022-02-08 17:02                                         ` Robert Pluim
2022-02-08 17:55                                         ` Dmitry Gutov
2022-02-08 17:08                                 ` Dmitry Gutov
2022-02-09  8:55                                   ` Robert Pluim
2022-02-08  9:52         ` João Távora [this message]
2022-02-08 10:19           ` Robert Pluim

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='CALDnm537vn56-gmKFxOr3pZ1VyVhx6Xd+koj=qU-uaUKqyyg1w@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=53853@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=leungbk@posteo.net \
    --cc=rpluim@gmail.com \
    /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).