public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: Larry McVoy <lm@bitmover.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 and BitKeeper
Date: Sat, 16 Mar 2002 01:31:34 +0100	[thread overview]
Message-ID: <20020316013134.A31470@devcon.net> (raw)
In-Reply-To: <20020315111022.S29887@work.bitmover.com> <Pine.LNX.4.33.0203151110130.29289-100000@penguin.transmeta.com> <20020315113001.W29887@work.bitmover.com>
In-Reply-To: <20020315113001.W29887@work.bitmover.com>; from lm@bitmover.com on Fri, Mar 15, 2002 at 11:30:01AM -0800

On Fri, Mar 15, 2002 at 11:30:01AM -0800, Larry McVoy wrote:
> 
> If you use vim and ctags, it sucks because I haven't yet taught vim how 
> to go from a read only revision controlled file to a read/write file.  
> It would be way cool if some vim genius out there showed me how to do
> that, I know it is possible, vim has the hooks, I simply don't have the
> time to go figure it out.

I'm certainly not a "vim genius", but somehow I managed to write some
vim autocmds that do this ;-)

You can get the vim script from

    http://www.myipv6.de/vim/extensions/bk.vim

Simply source it from your .vimrc. I tested it with vim 6.0 only,
although it should also work with prior versions.

On open, it tries to checkout a file from bitkeeper if it isn't
already checked out (doing "bk get" if you open it readonly and "bk
edit" otherwise), and it "bk edit"s the file if you start making
changes to a readonly bitkeeper controlled file.

Unfortunately, vim doesn't trigger the FileChangedRO autocmd if you do
a ":set readonly!" to go from readonly to read/write, so it doesn't
handle this case (AFAIK there is no way to intercept this command).

Andreas
-- 
       Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
     ---------------------------------------------------------
         +49 521 1365800 - af@devcon.net - www.devcon.net

  reply	other threads:[~2002-03-16  0:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14  4:42 Linux 2.4 and BitKeeper Marcelo Tosatti
2002-03-14  6:33 ` Ben Greear
2002-03-14  5:36   ` Marcelo Tosatti
2002-03-14  6:37   ` David S. Miller
2002-03-14  6:42   ` Larry McVoy
2002-03-14  7:54     ` Alex Riesen
2002-03-14 15:46       ` Larry McVoy
2002-03-14 18:10         ` Alex Riesen
2002-03-14 18:19     ` Ben Greear
2002-03-14 18:26       ` Robert Love
2002-03-14 18:40         ` Ben Greear
2002-03-14 22:56           ` Mark Frazer
2002-03-15 11:10     ` David Woodhouse
2002-03-15 16:04       ` Larry McVoy
2002-03-15 16:17         ` Stelian Pop
2002-03-15 17:58         ` Linus Torvalds
2002-03-15 18:16           ` Jeff Garzik
2002-03-15 18:27             ` Linus Torvalds
2002-03-15 18:47               ` Larry McVoy
2002-03-17  0:39                 ` Daniel Phillips
2002-03-17  5:42                   ` Mike Fedyk
2002-03-18 16:47               ` [PATCH] 2.5.7-pre2 IDE 22a Martin Dalecki
2002-03-15 18:39           ` Linux 2.4 and BitKeeper Larry McVoy
2002-03-15 19:01             ` Linus Torvalds
2002-03-15 19:10               ` Larry McVoy
2002-03-15 19:20                 ` Linus Torvalds
2002-03-15 19:30                   ` Larry McVoy
2002-03-16  0:31                     ` Andreas Ferber [this message]
2002-03-16  1:02                       ` Andreas Dilger
2002-03-15 16:10       ` David Woodhouse
2002-03-15  4:35 ` Stephen Torri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020316013134.A31470@devcon.net \
    --to=aferber@techfak.uni-bielefeld.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox