changeset 44687:bca57ad9e630

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
author Augie Fackler <augie@google.com>
date Thu, 09 Apr 2020 15:44:21 -0400
parents 90e05b304902
children 1b8fd4af3318
files tests/test-histedit-non-commute.t
diffstat 1 files changed, 3 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- 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 ..