Known issues

Commit mode and emacsclient

Magit recently switched from magit-log-edit-mode to git-commit-mode to edit commit messages. This caused a few problems (e.g. see this thread), and these issues are being investigated and addressed:

• 830 - I am VERY SORRY to have caused this breakage and I am taking full responsibility
• 805 - Magit cannot access Emacs server on Windows
• In progress 801 - magit-commit-internal still has serious quirks
• In progress 771 - Window management is awkward
• Full lists of related open and closed issues.

Commit popup

The command used to initiate a commit (c) is now a popup like other major commands. This was done for consistency with the rest of Magit and because it is no longer possible to turn on --amend while editing the message.

• 766 - Committing always pops the options buffer

Commit mechanism blocks other operation

This will be fixed. But we won't restore toggling between --amend/new commit while editing the message. Doing that makes very little sense.

• 827 - git-commit-mode prevents magit from running any other git operations in any repo

Commit popup key bindings

Unfortunately some bad key bindings were chosen in the key popup. -a was used to mean --amend but for consistency with git -a should mean --all. We are fixing this in two steps to avoid tears when someone presses -a and means --amend and not --all.

• Original mistake: -a => --amend, -A => --all
• Current: -r => --amend, -A => --all, -a unbound
• Goal: -r => --amend, -a => --all, -A unbound

Also see

• 783 - commit popup key bindings

Marmalade package

If you are using the development version of Emacs you have to also use the development version of Magit by either using Melpa or installing Magit from git. This is due to an incompatible change in delete-directory in Emacs-bzr.

• 684 - Eager macro-expansion failure: (wrong-type-argument listp 128)