condition-case: Suffix magit-log:--*-order is not defined or autoloaded as a command (interaction with native compilation?)) #4997
Replies: 14 comments 25 replies
-
(I have migrated this issue to a discussion, which technically closes the issue. That doesn't mean that I won't try to help.) Unfortunately I don't see how this is even possible to happen. My guess is that you have multiple versions of Magit sitting on the I don't think |
Beta Was this translation helpful? Give feedback.
-
I've had the same error for some time.
|
Beta Was this translation helpful? Give feedback.
-
@colonelpanic8 It's unclear what the exact reproduction steps are. (straight-bug-report
:interactive t
:post-bootstrap
(straight-use-package 'magit)) Use |
Beta Was this translation helpful? Give feedback.
-
I'd been struggling with this after rebuilding emacs from the emacs-29 branch on Ubuntu 22.04/x86_64 with GCC-12 based native comp. on. I added this to my init.el and it seems to be working now: |
Beta Was this translation helpful? Give feedback.
-
What package manager are you using? |
Beta Was this translation helpful? Give feedback.
-
FWIW, adding an ultra early demand of magit seems to fix the issue for me:
There must be some interaction with something else in my configuration, but theres just too much for me to bisect it and figure out where it is. |
Beta Was this translation helpful? Give feedback.
-
I don't know if it will help, but I have experienced something similar with magit-branch.el . I found that opening the file and eval-ing it fixed my issue. Will have to see if it returns when I restart emacs, but it seems as though the |
Beta Was this translation helpful? Give feedback.
-
Apologies for that, I was in a bit of a rush and thought a bit of extra info my assist,
To reproduce, seems to involve:
I admittedly do have a rather elaborate system using use-package and native compile. However, the issue appeared recently. I also get it when I try to push/pull. I deleted all the older packages and compiled files as far as I could see. |
Beta Was this translation helpful? Give feedback.
-
I also have this issue, using straight.el, emacs 29. like the OP, i manage sometimes to temporarily get rid of it (e.g. by removing all magit pkgs in straight dirs and rebuilding), but it comes back. i tried i tried the but if i i then moved all my magit config to much earlier in my init.el, right after straight/package things, and the issue went away also. (with no
i'll have to see if the issue remains solved with this workaround. |
Beta Was this translation helpful? Give feedback.
-
here: Following colonelpanic8 suggestion I solved with (use-package magit) |
Beta Was this translation helpful? Give feedback.
-
Emacs: 29.1, Straight: 2023-10-21 |
Beta Was this translation helpful? Give feedback.
-
Here's a fix for the impatient: On Elpaca (and Straight probably too), delete these paths: builds/magit
builds/magit-section
builds/transient Now go into the repos directories for transient and magit and check out: # in magit
git checkout v3.1.0
# in transient
git checkout v0.4.1 Now just restart Emacs and allow the normal bootstrapping to take place. Keep in mind, Straight will now hiccup from time to time when you try to update because it doesn't like detached heads. Magit depends heavily on Transient for command dispatch, so it makes sense that when they are out of sync, we can get odd issues with missing commands. I won't immediately investigate, but using transient and magit to bisect together may reveal where the issue is. I will leave it to the next person to find more up to date working versions. RememberAlways. Check dependency versions when having update / rollback issues. 🤓 Hope you learned your lessons 🤓 Elisp is no different than any other software ecosystem. Here is my tip jar for those who were convenienced: |
Beta Was this translation helpful? Give feedback.
-
lisp-interaction-mode is what you want. It has lexical-binding enabled.
Not supported.
You may be able to bypass that by adding
That sounds like a bug with that script. I'm not familiar with Nix, so I can't offer any more there.
The sub-process is started via |
Beta Was this translation helpful? Give feedback.
-
fyi, I had the same problem right now after upgrading from emacs 29.1 to 29.3 on MacOS. Using straight, it automatically rebuilt the packages (which were not version locked, unfortunately; also unfortunately I had excluded the .emacs.d/straight directory from my backups as I wrongly assumed that I would never need it...). Afterwards, the problem occurred. I tried every single solution mentioned in the long discussions so far, nothing helped (including fixing magit and transient to v3.2.1 and v0.4.1 respectively). Eventually I went into magit-log.el and manually deleted all occurrences of
|
Beta Was this translation helpful? Give feedback.
-
Some bindings/magit commands, specifically
magit-log
andmagit-remote
seem to be undefined.I have this feeling that somehow this could be user error/related to my configuration, BUT, I have done the following:
Now interestingly, rebuilding/restarting magit, DOES seem to fix the problem initially, but it seems to come back after a bit. I do have the auto-compile package enabled:
, so my suspicion is that it might somehow be related to that.
Again, sorry for filing this issue if this somehow really is related to my configuration, but I think it might just be an interaction with auto-compile and magit which seems like is something that shouldn't be happening. Feel free to close -- I completely understand if you don't think this is a magit issue, but I thought it might be useful to at least have something like this searchable in case other users come across something similar.
Version Info: Magit v3.3.0-736-g86b8491c, Transient 0.4.1, Git 2.32.0, Emacs 29.1, gnu/linux
Backtrace
Beta Was this translation helpful? Give feedback.
All reactions