Re: Bug with entering Log messages using editor other than vi
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Bug with entering Log messages using editor other than vi
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 background -- when you type gvim at the shell, you get another shell prompt immediately, as opposed to command-line vim, in which you don't get another shell prompt until you've quit the editor. But CVS needs its $EDITOR to run in the foreground; when the editor process exits, CVS knows it's time to read in the log message. Try setting EDITOR to gvim -f. That tells gvim to run in the foreground, which should make CVS happy. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Bug with entering Log messages using editor other than vi
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 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Bug with entering Log messages using editor other than vi
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 cvs thinks the editor was closed again. Maybe you find a switch in your editor to work with the file instead of a copy. If not you won't be able to use this editor I think. bye Fabi ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Bug with entering Log messages using editor other than vi
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 [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 $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 youre looking for faster http://search.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Bug with entering Log messages using editor other than vi
-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 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 Apparently, cvs thought gvim exited (and saved nothing to the temp file). 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 It looks like the problem is with gvim. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
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) 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 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. Regards __ Do you Yahoo!? Yahoo! Search - Find what youre looking for faster http://search.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
