cmdstate: introduce a "saver" contextmanager and use it in place of save() Previously, the state was only saved in some paths out of these functions. This can be problematic, if the user ctrl-c's (or `kill -9`'s) the process, or we exit out of `relocate` for anything besides the "expected" reason, we won't record that we were in the middle of an evolve. One of our users has discovered that this leaves hg in a weird state; the user did something like this: ``` $ hg evolve <something goes wrong with the merge tool, hits ctrl-c> <deals with the merge conflicts> $ hg evolve --continue abort: no interrupted evolve to continue $ hg evolve abort: uncommitted changes # Note: commands.status.verbose=True is set. $ hg status M foo # The repository is in an unfinished *update* state. # No unresolved merge conflicts # To continue: hg update ``` The user did an `hg update`, but it didn't actually do anything besides take it out of the unfinished update state (the files were still dirty in the working directory).

     1

SPHINXBUILD ?= sphinx-build

     2

     3

all: tutorials/tutorial.rst tutorials/topic-tutorial.rst static/logo-evolve.ico

     4

	$(SPHINXBUILD) . ../html/

     5

     6

tutorials/tutorial.rst: tutorials/tutorial.t test2rst.py

     7

	python test2rst.py tutorials/

     8

     9

tutorials/topic-tutorial.rst: tutorials/topic-tutorial.t test2rst.py

    10

	python test2rst.py tutorials/

    11

    12

static/logo-evolve.ico: static/logo-evolve.svg

    13

	convert -resize 36x36 static/logo-evolve.svg static/logo-evolve.ico