Read about our upcoming Code of Conduct on this issue

This instance will be upgraded to Heptapod 0.28.0 on 2022-01-18 at 14:00 UTC+1 (a few minutes of down time)

Commit 897d1fcc authored by Augie Fackler's avatar Augie Fackler
Browse files

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
parent 90e05b304902
......@@ -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 ..
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment