histedit: add test that an invalid editor doesn't bork client state
We had a report of a situation like this borking a user at Google, but
I can't reproduce it in a test. Let's at least backstop the issue with
a test, so we don't accidentally introduce such a bug...
Differential Revision: https://phab.mercurial-scm.org/D8391
--- a/tests/test-histedit-non-commute.t Tue Mar 31 23:25:26 2020 +0900
+++ b/tests/test-histedit-non-commute.t Thu Apr 09 15:44:21 2020 -0400
@@ -300,4 +300,7 @@
summary: Initial commit
+An invalid editor shouldn't leave the user in a broken state:
+ $ EDITOR=totally-not-a-thing-unsensible-editor-value hg histedit 4
+
$ cd ..