Replies: 3 comments 4 replies
-
|
This is a long list of seemingly unrelated errors. Some of them may be a consequence of transient erroring and then entering an inconsistent state. Other errors however, such as invalid read syntax, for example, are likely completely unrelated. Since eca was presumingly in large parts written by a LLM, you would first look there for defects. Again, its possible that there's something wrong in transient that needs fixing, but I don't see how I can help you with this from a distance. I recommend producing and studying a backtrace. Also, does transient still enter an inconsistent state, if you use a version after ecb2005? |
Beta Was this translation helpful? Give feedback.
-
|
To answer the last question first - yes. I track MELPA on my main machine and I've just hit the case again. It's certainly having eca enabled that gets me into the state but it always seems to be transient that gets stuck. It seems executing: from my console isn't enough to unwedge things. I'll try and get a better backtrace. |
Beta Was this translation helpful? Give feedback.
-
|
OK this is a cleaner log with transient debug enabled: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm not sure if the bug is in eca (see editor-code-assistant/eca-emacs#114) or transient but it certainly an interaction between the two which triggers the failure mode. Usually I'm in eca-chat and I trigger magit or another transient action and try to quit but something fails and I'm unable to navigate emacs because the keybindings are still in effect. However C-g or C-q don't quite the transient. Usually at this point I have to kill and restart emacs. The messages log shows transient commands getting run while I try to quit:
I can issue elisp via emacsclient so I would appreciate any hints on how find out why transient failed and didn't quit cleanly.
Beta Was this translation helpful? Give feedback.
All reactions