[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug with entering Log messages using editor other than vi
From: |
Larry Jones |
Subject: |
Re: Bug with entering Log messages using editor other than vi |
Date: |
Thu, 11 Mar 2004 22:55:35 -0500 (EST) |
g murkumar writes:
>
> the cvs would open a gvim editor window. AND at the
> same time say
> log message empty or unmodified
> a)abort c)continue....
CVS expects that the edit command will not complete until you've
finished editing the file. My guess is that gvim is one of those fancy
editors that opens a new window and then ends before you've even started
to edit the file, let alone finish. Such an editor is not suitable for
use as a CVS editor. You should check to see if gvim has a command line
option to make it behave as CVS expects. If not, you may be able to
achieve the same result by using a short script that runs gvim and then
does a "wait" command to wait for all child processes to finish before
continuing.
-Larry Jones
Somebody's always running my life. I never get to do what I want to do.
-- Calvin