Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jplindstrom (594)

jplindstrom
  (email not shown publicly)

Journal of jplindstrom (594)

Thursday November 20, 2008
06:50 PM

PerlySense does Git

[ #37915 ]

I just uploaded PerlySense 0.0160 to PAUSE after fixing the release script to not truncate trailing zeroes.

* Git support (Magit) for the Version Control commands. This means you can use the usual "Go To VCS Status" command for all (um, both) vcs backends.

* Fixed bug: Coverage visualization always instantiates an empty "covered" directory, even if there isn't any coverage to begin with.

* Fixed bug: Nothing happens after choosing between > 1 base classes in "Go to Base class" (response key named "class-description" instead of "class_description").

I chose Magit after experimenting with a few Emacs Git modules. Magit seems to support the full Git feature set well enough and still actually work in Emacs 22.

I'm not quite happy though, I also really need visual diffing a la ediff-buffers, and preferably something like the standard vc blame feature, which is truly awesome (the usefulness of the Version Control integration in Emacs is impressive enough to warrant a screencast some day).

vc with the git backend probably does this, but I'm not sure, and I think it might not work out of the box with Emacs 22.

If it's not supported at all, at least the ediff thing should be fairly easy to hack together.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If you interested, i wrote an article about work with Git from Emacs - it's available from my home page [xtalk.msk.su]

    Regarding Magit - i also have some ideas how to improve it and make it more "standard"

    P.S. for git blame information you can try to use git-blame.el

    • From my initial impressions, it doesn't quite do what the regular blame does.

      Revision highlighting inline in the source is nice and all, but that misses the point of viewing and comparing with earlier revisions.

      Maybe it does more than that, I couldn't really find any documentation for it.

    • That looks like a great article btw, I'll give it a read at lunch.