Re: Bug with entering Log messages using editor other than vi

[Paul Sander]

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 user
has finished editing the file so that it can copy the message into the
version history.  Changing editors to one that edits in the foreground
suddenly caused CVS to behave as you expect.

This is not a bug in CVS but rather an integration problem with your
tools.  I should think you have similar problems using a ~v command
while entering a message in a text-based mail client like mailx.

See if you can coax gvim to exit after you save your message.

--- Forwarded mail from address@hidden

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 at the
same time say

log message empty or unmodified:
a)abort c)continue e)edit !)use same message for all
directories

I would enter log message exit gvim and
say continue (i tried ! option also)

The problem was that NONE of my log messages were ever
registered even though the
cvs made successful updates of my changes, But i lost
my log messages, when i tried seeing cvs log
<filename>

Then i thought i'd change my $EDITOR in my .cshrc i
did so and made it 'vi' instead of gvim
...and Voila! the log messages started getting
registered. I didnt even get the

'log message empty or unmodified' error

Is this a bug? I wanted to bring this to the attention
of the developers so that
they may fix it, if it is a bug. If not please advise
what was wrong on my part.

--- End of forwarded message from address@hidden