[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bitkeeper-users
Subject:    Re: [Bitkeeper-users] Early integration between BitKeeper and Emacs
From:       Larry McVoy <lm () bitmover ! com>
Date:       2003-03-27 23:12:09
[Download RAW message or body]

As this gets more evolved, and with your permission, we would be happy to
bundle it with BK and/or host a BK repo here to maintain it.  Thanks for
doing this.

--lm

On Thu, Mar 27, 2003 at 03:05:39PM -0800, Bryan O'Sullivan wrote:
> If you're an Emacs or XEmacs user, you'll have noticed that the
> integration between BK and Emacs is, um, minimal.  I've got the
> beginnings of some useful integration between the two in place, which
> I'm releasing in the twin hope that (a) someone else will find it useful
> and (b) someone else will want to contribute changes.
> 
> Right now, functionality is fairly minimal, but still useful.
> 
>       * It tells you, in the modeline, which BK license applies to the
>         repo you're working in.  This is a lot easier than looking in
>         BitKeeper/etc/config.
>       * You can register files properly, which doesn't work at all under
>         vc.el.
>       * It turns off a few unsupported VCisms, such as snapshot support.
> 
> Missing is everything else useful, such as revision histories, firing
> off GUI tools, and so on, but I do intend to add that kind of stuff.
> 
> One caveat: the code works under XEmacs 21.4, but will need a bit of
> tweaking to work under GNU Emacs.  The versions of VC maintained across
> both Emacsen are heinously forked.
> 
> Comments welcome, patches even more so.  If there's actual
> non-negligible interest, I'll make an anonymous BK repo available.
> 
> 	<b



-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm
_______________________________________________
Bitkeeper-users mailing list
Bitkeeper-users@bitmover.com
http://bitmover.com/mailman/listinfo/bitkeeper-users
To unsubscribe from this list, go to the above URL, follow instruction at the bottom of the web page.
[prev in list] [next in list] [prev in thread] [next in thread]