From: Adria Farres <14farresa@gmail.com>
To: git@vger.kernel.org
Subject: --trust-exit-code not working
Date: Fri, 14 Nov 2014 17:12:35 +0100 [thread overview]
Message-ID: <20141114161235.GA30086@vimeitor> (raw)
Hello!,
I sent an email last week, but I'm not sure if I sent it incorrectly, or the
formatting was very bad, or it went unnoticed. A few days ago a great soul was
kind enough to create the --trust-exit-code option that made git respect the
exit code of the difftool. Unfortunately, I haven't been able to make it work.
Exiting vimdiff with :cq doesn't seem to make git quit, as it keeps pushing new
files to be diffed. I tried meld and the exact same thing. I'm confident that
exiting with :cq gives an error, as I have checked it, and I'm using git
2.2.0.rc1.
Am I missing something important? Has anyone managed to make it work with
vimdiff and meld? Sorry for bringing that up so late and for being a
disturbance.
Thank you,
Adria
next reply other threads:[~2014-11-14 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 16:12 Adria Farres [this message]
2014-11-14 20:41 ` --trust-exit-code not working Junio C Hamano
2014-11-14 21:07 ` David Aguilar
2014-11-14 21:55 ` David Aguilar
-- strict thread matches above, loose matches on Subject: below --
2014-11-08 17:23 Adri Farr
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=20141114161235.GA30086@vimeitor \
--to=14farresa@gmail.com \
--cc=git@vger.kernel.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).