It is not necessary to use magit for this particular operation - vanilla emacs can do it.
(Also, because this uses vc, this should work identically in any version control system that vc supports.)
First, use the vc-annotate command, which is bound to the key sequence C-x v g.
Now, the point should be at the commit id that you are interested in. (If not, you might need to use C-x 1 and/or v so that you can see which line is which, in order to navigate to the right one.) You might be able to see the diff for that file using = now - if you get an error beginning with "cannot diff from any revision prior...", that probably means that this revision created the file (and that's probably a bug in emacs).
The author and date are already visible in the Annotate buffer that vc-annotate produced.
To see the commit message, press l (the letter, not the number 1) in the Annotate buffer. To see what the file looked like at that revision, press f in either the Annotate buffer or the vc-change-log buffer.
I'd suggest the use of magit-blame-mode (M-x magit-blame-mode). It provides the information in much nicer manner compared to vc-annotate and is part of the standard magit distribution. You'd probably want to bind it to some keyboard combination to toggle it quickly.
In magit-blame-mode use p and n to navigate between the previous and the next change and RET to see the diff for a particular commit.
vc-annotate output (or any traditional blame output) much more readable than this, personally; but it's always good to have alternatives.
vc-annotate.
v to hide the details, you still have the age color coded blame.
magit-blame-mode pretty much unreadable in the way it mixes/interleaves code and commit history. Is there a way to get it to show output like vc-annotate (or git blame, or indeed any other readable format where the code is separate from the annotation)?
magit-blame-mode doesn't have the main useful feature of vc-annotate, its 'A' (annotate at the revision previous to the current line). So that's another reason to prefer vc-annotate at this point, as awesome as magit is otherwise.
Follow WeChat
Success story sharing
Want to stay one step ahead of the latest teleworks?
Subscribe Now相似问题
- How to modify existing, unpushed commit messages?
- View the change history of a file using Git versioning
- What is the difference between 'git pull' and 'git fetch'?
- How do I undo 'git add' before commit?
- Commit only part of a file in Git
- Move the most recent commit(s) to a new branch with Git
- How do I delete a Git branch locally and remotely?
- How do I revert a Git repository to a previous commit?
- How do I rename a local Git branch?
ais the money action -- show blame before that change. Saves me so much time.vc-annotatemakes more sense to me thanmagit-blame-mode.vc-annotateis in many ways better than that ofmagit-blamethe latter is much faster, which swings it for me.