On Mon, Oct 12, 2009 at 5:13 PM, Shawn O. Pearce <spearce@xxxxxxxxxxx> wrote: > Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: >> The problem is that gvim returns immediately > ... >> (BTW, this is in no way specific to Git, 99% applications calling >> $EDITOR will expect the same behavior) > > The sad part is, every gvim user blames Git. > > Every single one of my coworkers who uses Linux had gvim as their > default $EDITOR and found git commit working sometimes, and not > working others. Since git was new to them, they blamed git, not > their $EDITOR. They also felt insulted when I told them their > $EDITOR was busted and should be replaced. > > Someone needs to whack gvim upside the head and fix that program > to behave correctly. Huh? What is wrong about 'gvim --nofork'? -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html