From: Felipe Contreras Date: Mon, 12 Oct 2009 14:36:50 GMT Subject: Re: git refuses to work with gvim Message-ID: <94a0d4530910120736p4cc310c0id08765ab5f10d0a3@mail.gmail.com> In-Reply-To: <20091012142523.GH9261@spearce.org> On Mon, Oct 12, 2009 at 5:25 PM, Shawn O. Pearce wrote: > Felipe Contreras wrote: >> On Mon, Oct 12, 2009 at 5:13 PM, Shawn O. Pearce wrote: >> > >> > Someone needs to whack gvim upside the head and fix that program >> > to behave correctly. >> >> Huh? What is wrong about 'gvim --nofork'? > > The fact that its a command line option that isn't the default. > gvim's UI here is as bad as pre 0.99 git. > > People do: > >        export EDITOR=gvim > > and things work OK for a while, as they always open a new editor, > work with the file, and then close it, killing the only running gvim > session.  Since gvim waits if its the only gvim process running, > things seem fine.  But days later when you leave a file open, > suddenly the command calling $EDITOR starts failing. I've never seen it happening. For me either it aways fails (fork) or always work (nofork). > I've seen it happen to a lot of people.  They just start complaining > about how one day "git commit" is fine, and the next day its > not working.  But its been weeks since they selected gvim as their > $EDITOR and they can't connect the open editor window as the problem > with that Goddamn Idiotic Truckload of s**t they are forced to use. Yeah, it happened to me too, but eventually I realized what was happening. I like gvim's default behavior tough. I personally don't see any problem... how about other SCMs? -- Felipe Contreras