-
Notifications
You must be signed in to change notification settings - Fork 0
Known issues
Also see the FAQ and the list of all outstanding issues.
Definitely, soon. But the issues in the following milestones have to be addressed first: a, b. We will enter feature freeze soonish.
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.
The main benefit of the new workflow is that we can avoid duplicating functionality available from git. But unfortunately it only works when Emacsclient knows how to connect to the Emacs server. Also some features of the old commit mode have not yet made their way to the new mode.
The old workflow might be partially restored by offering vc-git-log-edit as an option. Nothing decided yet.
Magit recently switched from magit-log-edit-mode to git-commit-mode to edit commit messages. This caused a few problems, and these issues are being investigated and addressed.
- In progress 801 - magit-commit-internal still has serious quirks
- Windows should be fixed 805 - Magit cannot access Emacs server on Windows
- OS X
- Full lists of related open and closed issues.
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. Some people who have initially complained about this eventually come to prefer the new way; hang in there once you have unlearned the old key bindings you might like the change too.
This will be fixed. Doing so involves addressing the oldest open issue, and there is a reason that has been open for so long. It is still possible to display a diff while editing the message but it is not possible to e.g. edit two commit messages in different repositories at the same time.
- 827 - git-commit-mode prevents magit from running any other git operations in any repo
- 24 - magit only supports one Git process at a time
This change will not be reverted. It makes little sense to do that while editing the commit message. One reason for that is that one doesn't get the old message when turning on amending while already in the message buffer.
Also doing so is actually impossible with the new commit workflow. --amend now has to be toggled in the commit popup or using a prefix argument to magit-commit.
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. To avoid tears when someone presses -a and means --amend and not --all we have fixed this in two steps. The new bindings are -r for --amend and -a for --all, -A is unused.
That isn't Magit's fault. The new commit workflow involves visiting a file so all the relevant hooks are run. You likely have some package installed that remembers point. We have a kludge that works around this for the built-in saveplace package, but we won't add similar kludges for other packages.
- wontfix 31@git-modes