You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
consult-mu stop to be executed due to consult API upgrade
To Reproduce
Steps to reproduce the behavior:
M-x consult-mu (with the latest consult mode, in my case, the consult version is consult-20250105.2058)
Got error message:
CONSULT ERROR: consult-mu' uses the old async API convention and must be updated. The consult--async-*' API has been updated in a
backward-incompatible way. For details, please see the Consult
CHANGELOG, the relevant git commit message and the docstring of the
`consult--async-pipeline' macro, which describes the updated API.
Important Information:
OS: Debian 12
Version of Emacs: 31.0.50(built with the latest source code)
Version of mu: 1.12.8
Version of consult : 20250105.2058
The text was updated successfully, but these errors were encountered:
@ruanxiang Thanks for reporting this. I am aware of the breaking changes that minad pushed recently. I need some time before to go over changes and update/adapt to the new API. In the meanwhile, you have to use consult stable releases (1.8 or 1.9 should work just fine). Let me know if you run into any issues with the stable releases while I work on the latest changes.
Describe the bug
consult-mu stop to be executed due to consult API upgrade
To Reproduce
Steps to reproduce the behavior:
M-x consult-mu (with the latest consult mode, in my case, the consult version is consult-20250105.2058)
Got error message:
CONSULT ERROR:
consult-mu' uses the old async API convention and must be updated. The
consult--async-*' API has been updated in abackward-incompatible way. For details, please see the Consult
CHANGELOG, the relevant git commit message and the docstring of the
`consult--async-pipeline' macro, which describes the updated API.
Important Information:
mu
: 1.12.8consult
: 20250105.2058The text was updated successfully, but these errors were encountered: