Hot answers tagged

3

When you use p to set the value of branch.<name>.pushRemote "the value has to be the name of an existing remote", and so you can only enter one of those. It's quite common for there to only be origin, in which case that is the only valid value. If you wish to add new remotes, use the Remotes popup bound to M. Note that the remote branch for your ...


3

Wow, it's almost too easy. Just go to the other commit in the log buffer, show it, and use "a" to apply each change to the current working dir.


2

Solution: Set magit-todos-exclude-globs variable. It can be set globally by (setq magit-todos-exlude-globs '(pattens)) in config or locally, per-repository. To set it locally, run add-dir-local-variable, choose magit-status-mode, choose magit-todos-exclude-globs, add patterns you would like to exclude as a list. Example: ("*.map" "*.html") That will ...


1

If you type M-x describe-char with point on a commit hash, you can see various informations about the character, including its face: There are text properties here: face magit-hash Now you can move the point (using the TAB key) to the face name and type the RETURN key (or click on the words magit-hash) to get the face's documentation....


1

The --show-signature argument can be selected in the log popup but it is not actually passed to git log. Instead %G? is added to the value of the --format= argument. That (%G?) causes some letter to be printed for each commit and the code that parses the log output detects that letter and uses it to determine what face should be used to display the commit ...


1

If you want to store that in your config, like me, just add (setq magit-diff-refine-hunk (quote all)) to your .emacs.d/init.el This was inspired by phils' answer.


Only top voted, non community-wiki answers of a minimum length are eligible