From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 23 Sep 2016 15:37:00 GMT
Subject: Re: Limitiations of git rebase --preserve-merges --interactive
Message-ID: <xmqqvaxm1vc3.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <1mu13z0.1hye7bq1uqj26sM%lists@haller-berlin.de>

lists@haller-berlin.de (Stefan Haller) writes:

> Thanks, this is interesting; I'm having trouble understanding the tests
> though. Some of them use rebase -p -i, but I don't understand why they
> use -i, or why that even works in a test (i.e. why it doesn't open an
> editor).

Upon starting up, tests dot-source t/test-lib.sh file and it
unsets most of GIT_* environment variables to obtain a stable
testing environment that is not affected by things that testers
may have in their environment.

There is EDITOR=: in t/test-lib.sh, which was added in 2006 before
GIT_EDITOR was invented.  That is the one in effect for git
subcommands that usually interacts with editors during the test,
unless specific tests further override it with test_set_editor
helper.