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

From:

Eric Siegerman

Subject:

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

Date:

Thu, 11 Mar 2004 17:11:29 -0500

User-agent:

Mutt/1.2.5i

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. address@hidden
| | /
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