bug#60812: 29.0.50; error when using doom-modeline-mode and flymake-mode

[Stefan Kangas]

Arash Esbati <arash@gnu.org> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Paul Nelson <ultrono@gmail.com> writes:
>>
>>> Starting from emacs -Q, I enter the following commands via M-x:
>>>
>>> package-initialize
>>> doom-modeline-mode
>>> flymake-mode
>>>
>>> This yields the following in *Messages*:
>>>
>>> Doom-Modeline mode enabled
>>> Flymake mode enabled in current buffer
>>> error in process sentinel: apply: Symbol’s value as variable is void:
>>> flymake--backend-state
>>> error in process sentinel: Symbol’s value as variable is void:
>>> flymake--backend-state
>>>
>>> flymake seems to function OK for me now even with this error, but it wasn't
>>> earlier; I haven't been able to reproduce a situation in which it doesn't
>>> function, but the above error message was the only one that I saw, and it
>>> seems to have been caused by doom-modeline-mode.
>>
>> I'd suggest reporting this to the doom-modeline-mode developers first.
>
> doom-modeline-segments.el contains these lines:
>
> ;; Compatibility
> ;; @see 
> https://github.com/emacs-mirror/emacs/commit/6e100869012da9244679696634cab6b9cac96303.
> (with-eval-after-load 'flymake
>   (unless (boundp 'flymake--state)
>     (defvaralias 'flymake--state 'flymake--backend-state))
>   (unless (fboundp 'flymake--state-diags)
>     (defalias 'flymake--state-diags 'flymake--backend-state-diags)))
>
> Maybe updating the package is sufficient.
>
> Best, Arash

No further comments within 9 months, so I'm assuming upgrading and/or
reporting this to the doom-modeline-mode developers worked.

I'm therefore closing this bug report.

If this conclusion is incorrect and this is still an issue, please reply
to this email (use "Reply to all" in your email client) and we can
reopen the bug report.