It sounds like the gvim program is launching your edit session in the
background and then exiting. You can create the same effect with vi
by using the following script as your editor:
#!/bin/sh
xterm -e vi $1
CVS relies on the exit of the editor process as a signal that the
On Mon, Mar 08, 2004 at 06:06:44PM -0800, g murkumar wrote:
$cvs commit
the cvs would open a gvim editor window. AND at the
same time say
log message empty or unmodified:
a)abort c)continue e)edit !)use same message for all
directories
The problem is that gvim forks and runs in the
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
the cvs would open a gvim editor window. AND at the
same time say
log message empty or unmodified
a)abort c)continue
I guess it's about how editors handle files. Some work with the file itself,
others make a copy in /tmp and work with this. So the original file is
immediately released. And
in the foreground.
- Original Message -
From: g murkumar [EMAIL PROTECTED]
Date: Monday, March 8, 2004 4:13 pm
Subject: Bug with entering Log messages using editor other than vi
Background :
PC :Intel Pentium 4
OS :Linux redhat 9
CVS version: 1.11.13 (client/server)
Initially my
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf
Of g murkumar
Sent: Monday, March 08, 2004 7:13 PM
To: [EMAIL PROTECTED]
Subject: Bug with entering Log messages using editor other than vi
Initially my $EDITOR environment variable was set to
gvim
Background :
PC :Intel Pentium 4
OS :Linux redhat 9
CVS version: 1.11.13 (client/server)
I am using latest sources of stable version
Initially my $EDITOR environment variable was set to
gvim
After making changes to a OR many files i do
$cvs commit
the cvs would open a gvim editor window. AND
