Skip to content

Change the suffix for magit-dispatch to avoid an error#767

Closed
jmcarcell wants to merge 1 commit intomagit:mainfrom
jmcarcell:fix-magit-dispatch-error
Closed

Change the suffix for magit-dispatch to avoid an error#767
jmcarcell wants to merge 1 commit intomagit:mainfrom
jmcarcell:fix-magit-dispatch-error

Conversation

@jmcarcell
Copy link
Copy Markdown

I have updated to the last version of magit and forge and I'm finding the following error:

Error (use-package): forge/:catch: Cannot insert ("N" "Forge" forge-dispatch) into magit-dispatch; o not found

There is a related issue: #388
and this solution is the same as highlighted in one of the comments:
#388 (comment)
After this change the error doesn't appear anymore.

The error is the following:
```
Error (use-package): forge/:catch: Cannot insert ("N" "Forge" forge-dispatch) into magit-dispatch; o not found
```
There is a related issue: magit#388
and this solution is the same as highlighted in one of the comments:
magit#388 (comment)
@tarsius
Copy link
Copy Markdown
Member

tarsius commented Apr 15, 2025

You forgot to mention that this happens because you are using evil-collection.

The suffix in magit-dispatch are sorted alphabetically by key. I do not know to what extend evil-collection messes that up, but it does not make sense to insert this command out-of-order for everyone, just for the benefit of evil-collection users.

Failure to insert a suffix did not result in an error until recently. I have now gone back to that behavior by default, see magit/transient#374.

evil-collection should be adjusted to add forge-dispatch to magit-dispatch in a location and using a key that is appropriate when using evil.

@tarsius tarsius closed this Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants