Sergei Organov <osv@xxxxxxxxx> writes: > David Kågedal <davidk@xxxxxxxxxxxxxx> writes: > >> Sergei Organov <osv@xxxxxxxxx> writes: >> >>> Then there should be (require 'format-spec) in git-blame.el, right? Due >>> to: >> >> Of course. I must have missed that since I already had it loaded. >> >>> Now, I've evaluated (require 'format-spec) in my Emacs 22 (yes, 22, not >>> 23), and now git-blame almost works there. The problem I see is that it >>> doesn't output anything in the echo area. It color-codes the buffer, it >>> does show correct pop-up when mouse is over a region, but it doesn't >>> print anything in the echo area when I move cursor through the regions. >>> Any idea how to debug/fix this? >> >> Well, it appears I removed the output to the echo area. I didn't think >> it worked very well, and the new output format mostly replaces it by >> showing the hash. >> >> There are also technical reasons for removing it (it couldn't be >> implemented very cleanly). > > I didn't know you deliberately removed it, -- I thought it's some > Emacs22 - related problem. I have no problem then, except that I don't > know how to get the hash into my kill-ring or X selection. > > While we are at it, why is git-blame-identify interactive and how is it > useful? I think I need to go over this file with a fine-tooth coam to remove or fix bitrot. This command seems to try to show the hash in the echo area, but probably doesn't work. New and better commands should be deviced. I'll try to find some time to work on this soon. Thanks a lot for the feedback. -- David Kågedal -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html