A pull request I just sent in: https://github.com/philjackson/magit/pull/171 a.k.a. git://github.com/pjweisberg/magit.git link-commits ====================================================================== When a commit message mentions another commit by its SHA1 hash, put the magit-log-sha1 face on it, and allow the user to visit the referenced commit by putting the cursor on it and pressing RET. (I also did the same thing for the two parents in a merge commit.)
It picks out only hashes that actually are other commits. So in the phrase "Elvis is dead," "dead" would be highlighted if and only if dead uniquely identifies a commit in the repository. In the phrase "Zombies are deader than vampires," "dead" would never be highlighted because of the non-hex digit in the word. To make it easier to get back to where you were I added "back" and "forward" buttons to the commit buffer. ====================================================================== Someone mentioned on this list that keybindings were a controversial topic, so I thought I'd mention this here, because I bound those "back" and "forward" functions I added to <M-left> and <M-right> in the commit buffer. (Firefox and Chrome use those keys for back and forward.) However, magit-mode already binds <M-left> to magit-goto-parent-section. Does that seem like an acceptable change, or should I pick a different binding? -PJ
