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

[Charlie Farbstein]

You need to set the EDITOR or CVSEDITOR environment variable to 
  "gvim -f"
The vim mailing list had a long discussion on this topic a few months
ago.  The bottom line is that gvim behaves differently than other X
applications and automatically forks its gui.  The -f option forces gvim
to run in the foreground.



----- Original Message -----
From: g murkumar <address@hidden>
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 $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....
> 
> I would enter log message exit gvim and
> say continue (i tried ! option also)
> 
> The bug 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.
> 
> THen i thought id change my EDITOR in my .cshrc i did
> so and made it vi
> 
> 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 not please advise what was wrong
> on my part.
> Regards
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you’re looking for faster
> http://search.yahoo.com
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
>