all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Martyanoff <khaelin@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Nicolas Martyanoff <khaelin@gmail.com>, 53843@debbugs.gnu.org
Subject: bug#53843: 27.2; unknown function used in flymake
Date: Mon, 07 Feb 2022 15:50:03 +0100	[thread overview]
Message-ID: <87leymzq78.fsf@valhala.localdomain> (raw)
In-Reply-To: <877da692j4.fsf@gmail.com> (Robert Pluim's message of "Mon, 07 Feb 2022 15:25:51 +0100")

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Mon, 07 Feb 2022 13:54:23 +0100, Nicolas Martyanoff <khaelin@gmail.com> said:
>
>     Nicolas> Hi,
>
>     Nicolas> Using eglot with python-mode (with pyright) causes regular errors
>     Nicolas> involving flymake caused by calls to an unknown "string-replace"
>     Nicolas> function:
>
> `string-replace' was added in emacs-28, so it looks like your flymake
> package needs adjusting. (the version shipped with emacs-28 has ;;
> Package-Requires: ((emacs "28.1") (eldoc "1.1.0") (project "0.7.1")))

I am using eglot which references a flymake copy from
https://github.com/emacs-straight/flymake.

The author of eglot told me to report the bug here, but I guess the
problem comes from eglot (which requires 26.1+) using a copy of flymake
which requires (28.1+).

I do not understand why emacs loads this copy of flymake without
signaling an error given the constraint in Package-Requires, or why is
eglot using a copy of flymake altogether, but these problems are
unrelated to string-replace.

Thank you for the information anyway!

Regards,

-- 
Nicolas Martyanoff
http://snowsyn.net
khaelin@gmail.com





  reply	other threads:[~2022-02-07 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 12:54 bug#53843: 27.2; unknown function used in flymake Nicolas Martyanoff
2022-02-07 14:25 ` Robert Pluim
2022-02-07 14:50   ` Nicolas Martyanoff [this message]
2022-02-07 15:05     ` Robert Pluim
2022-02-07 15:28       ` Nicolas Martyanoff
2022-02-07 15:44         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87leymzq78.fsf@valhala.localdomain \
    --to=khaelin@gmail.com \
    --cc=53843@debbugs.gnu.org \
    --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 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.