unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: 69809@debbugs.gnu.org
Subject: bug#69809: 30.0.50; flymake: error in process sentinel
Date: Fri, 15 Mar 2024 08:09:40 +0100	[thread overview]
Message-ID: <m25xxonf7v.fsf@Pro.fritz.box> (raw)

In master, I am sometimes getting errors like these:

  error in process sentinel: flymake--handle-report: Can’t find state for flymake-cc in ‘flymake--state’
  error in process sentinel: Can’t find state for flymake-cc in ‘flymake--state’
  error in process sentinel: flymake--handle-report: Can’t find state for flymake-cc in ‘flymake--state’
  error in process sentinel: Can’t find state for flymake-cc in ‘flymake--state’
  error in process sentinel: flymake--handle-report: Can’t find state for flymake-cc in ‘flymake--state’
  error in process sentinel: Can’t find state for flymake-cc in ‘flymake--state’

when working with C files.

I haven't configured anything for Flymake myself. I think Flymake gets
involved by using Eglot. The errors apparently don't prevent flymake
from working later on.

I have looked around in flymake docs and source, but I can't figure out
what's wrong.






             reply	other threads:[~2024-03-15  7:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  7:09 Gerd Möllmann [this message]
2024-03-21 10:23 ` bug#69809: 30.0.50; flymake: error in process sentinel Eli Zaretskii
2024-03-23 14:02   ` sbaugh
2024-03-23 14:20     ` Gerd Möllmann
2024-07-11  9:45       ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-11 11:15         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-11 11:46           ` Gerd Möllmann
2024-07-12  6:27           ` Eli Zaretskii
2024-07-16 20:48             ` Spencer Baugh
2024-07-17  6:12               ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17  8:20                 ` João Távora
2024-07-17  9:07                   ` João Távora
2024-07-17 13:08                     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17 13:44                       ` João Távora
2024-07-17 17:25                         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-17 17:38                           ` João Távora
2024-07-17 23:54                             ` João Távora
2024-07-18  0:10                               ` João Távora
2024-07-24 16:25                               ` Spencer Baugh
2024-07-25  7:28                                 ` Eli Zaretskii
2024-07-25  7:45                                   ` João Távora
2024-07-25 10:50                                     ` Eli Zaretskii
2024-07-25 11:49                                       ` João Távora
2024-07-27  7:26                                         ` 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

  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=m25xxonf7v.fsf@Pro.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=69809@debbugs.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.
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).