* non-interactive rebase opens vim
@ 2011-02-23 13:21 Marc Strapetz
2011-02-23 13:38 ` Marc Weber
0 siblings, 1 reply; 2+ messages in thread
From: Marc Strapetz @ 2011-02-23 13:21 UTC (permalink / raw)
To: git
I've started a non-interactive rebase (of 3 commits) which results in a
conflict for the first commit. After resolving the conflict, I've invoked
git rebase --continue
which brings up vim. I would not expect that. The main problem with this
behavior is that, when invoked from our GUI client, this results in the
client hanging forever. What forces git to open vim and how can I avoid
that?
git version 1.7.3.1.msysgit.0
--
Best regards,
Marc Strapetz
=============
syntevo GmbH
http://www.syntevo.com
http://blog.syntevo.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: non-interactive rebase opens vim
2011-02-23 13:21 non-interactive rebase opens vim Marc Strapetz
@ 2011-02-23 13:38 ` Marc Weber
0 siblings, 0 replies; 2+ messages in thread
From: Marc Weber @ 2011-02-23 13:38 UTC (permalink / raw)
To: git
Excerpts from Marc Strapetz's message of Wed Feb 23 14:21:08 +0100 2011:
> which brings up vim. I would not expect that. The main problem with this
> behavior is that, when invoked from our GUI client, this results in the
> client hanging forever. What forces git to open vim and how can I avoid
> that?
Maybe use gvim --nofork as editor?
Its not a true fix.. but the most simple workaround which comes to my
mind.
Marc Weber
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-02-23 13:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-23 13:21 non-interactive rebase opens vim Marc Strapetz
2011-02-23 13:38 ` Marc Weber
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).