From: Felipe Contreras <felipe.contreras@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
sebastian@coli.uni-sb.de, git@vger.kernel.org
Subject: Re: git refuses to work with gvim
Date: Mon, 12 Oct 2009 17:20:19 +0300 [thread overview]
Message-ID: <94a0d4530910120720pccaa920n7ab407494473ac7b@mail.gmail.com> (raw)
In-Reply-To: <20091012141334.GE9261@spearce.org>
On Mon, Oct 12, 2009 at 5:13 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> 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
next prev parent reply other threads:[~2009-10-12 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 11:43 git refuses to work with gvim sebastian
2009-10-12 12:43 ` Matthieu Moy
2009-10-12 14:13 ` Shawn O. Pearce
2009-10-12 14:20 ` Felipe Contreras [this message]
2009-10-12 14:25 ` Shawn O. Pearce
2009-10-12 14:36 ` Felipe Contreras
2009-10-12 18:29 ` Joshua Roys
2009-10-12 17:37 ` Markus Heidelberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94a0d4530910120720pccaa920n7ab407494473ac7b@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=sebastian@coli.uni-sb.de \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).