this post was submitted on 10 Oct 2023
1 points (100.0% liked)

Emacs

311 readers
3 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
[email protected]
[email protected]
1
Magit hiccup : transient-setup: Suffix (alien.top)
submitted 1 year ago by [email protected] to c/[email protected]
7 comments fedilink hide all child comments
 

(caveat: I have only briefly reviewed changelogs and didnt spot anything)

I just fired up magit to merge my dev branch into master, and somehow the keys have changed or are not working. I used to hit "b l" to checkout a local branch (in this case master) where I'd then merge dev into it, push it to github, and then checkout out dev again.

I get this message:-

​

"transient-setup: Suffix magit-branch..merge/remote is not defined or autoloaded as a command"

Hopefully someone here has recently done the slog and can save this lazy individual some time. What changed? I havent touched my magit setup for literally years.

(magit-checkout from minibuffer works fine).

​

GNU Emacs 29.1.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.24.37, cairo version 1.16.0) of 2023-08-10

straight package manager.

​

​

top 7 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 year ago (1 children)

You didn't mention which Emacs Version, package manager, etc.

[–] [email protected] 1 points 1 year ago (1 children)

A very good point and stupid of me. added. That said, if someone else has seen this error they'll recognise it.

[–] [email protected] 1 points 1 year ago (1 children)

https://github.com/magit/magit/discussions/4997#discussioncomment-7050963

What's needed is a reproduction case. There are people claiming the bug affects them with both package.el and Straight. I've not encountered the bug myself, and frankly can't be bothered to dig into it if the people who are seeing it can't provide a repro.

[–] [email protected] 1 points 1 year ago

Then dont. This was merely asking if someone has solved it. Thanks for the link.

[–] [email protected] 1 points 1 year ago (1 children)

A. Upgrade all the upgradable packages.

B. Downgrade to a known-good set of packages.

C. File a bug report (but only after trying A).

Those are your choices.

[–] [email protected] 1 points 1 year ago

Downgrading to a "known set" of good packages is a lot of work requiring time galore.

The other option is someone else has come across this and has a solution.

[–] [email protected] 1 points 1 year ago

idk if you found a solution but i just had the same problem after a mass package update i did. To solve it, I deleted magit-* from .emacs.d/elpa (i.e. all the cached files), restarted emacs and after it re-downloaded magit, problem was gone.