# HG changeset patch
# User Augie Fackler <augie@google.com>
# Date 2020-04-09 19:44:21
# Node ID bca57ad9e630a7de4f3a76ec6cbc5dc489f2d154
# Parent  90e05b3049022568f05e5649699762dc2571c771

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

diff --git a/tests/test-histedit-non-commute.t b/tests/test-histedit-non-commute.t
--- a/tests/test-histedit-non-commute.t
+++ b/tests/test-histedit-non-commute.t
@@ -300,4 +300,7 @@ post message fix
      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 ..