For visual consistency with diff-mode
…olor-theming Just as org inherits various faces from outline-mode, there are plenty of built-in faces which can serve as a logical base for magit's faces. This patch adds :inherit to several faces, and there may be an opportunity to add more. Failing to inherit faces where it is reasonable to do so means that magit is likely to look odd for users who have installed custom color-themes, which typically only redefine the more basic faces.
…ecific error message.
… call magit-status interactively instead of asking to create a git repository in the current directory.
…existing frame. Also added some --help text to let people know what the option is
…ng. I was losing the error code from the first part of the pipeline.
The version number is set to the output of `git describe --tags --dirty`. If the current HEAD is tagged (as released version are), then that will be the name of the tag. Otherwise it will be the tag name, plus the number of commits on top of that tag, plus a short hash of the exact commit, plus "-dirty" if there are changes in the working tree. Thus, the version number will actually tell us the exact version being used when a development snapshot is installed The Makefile's `dist` and `install` targets will substitute in the proper version numbers when they create files to be used outside the Git directory. bin/mk_rel.bash has been simplified greatly, since there's no longer any consistency checking for it to do.
Add an autoload magic comment to the command that sets up the git-rebase-todo buffer to automatically switch to rebase-mode. For users who use the autoloads, this will update auto-mode-alist before rebase-mode.el is loaded.
This accomplishes what 2ba651c did but in a way consistent with other sections and so that auto-more-entries (see the next commit) can be easily added.
You can get the old magit-status behaviour back by using switch-to-buffer.
Requires the third argument to add-hook, because `ediff-cleanup-mess` relies on buffer-local variables, so `magit-ediff-restore` must run *after* it.
…ead-file-from-rev` more than once per revision. The results of prior calls are stored in an alist called `magit-tree-contents-cache-internal`.