to abort / to continue (UX)

[timeless]

timeless wrote:
> technically this isn't wonderful, if you use bookmarks, `hg up -C .`
> isn't equivalent to `hg up -C {currentbookmark}`, and if you're using
> hg-git or something that puts significant weight on your active
> bookmark, this can lead you into some very unfortunate weeds.

Martin von Zweigbergk wrote:
> Good point. There's just no correct way of aborting yet, is there? I suppose
> we'll have "hg abort" some day. "hg update -C ." always felt a little
> git-like to me in the it reuses a command that happens to be closest
> implementation-wise.

Yeah, `hg abort` is sort of the right pair to `hg continue`. And we're
only slowly approaching `hg continue` (actually, we're probably
moderately close).

I think we could probably at least write a helper to make the "to
abort" case work on average. Bookmarks could register to replace `.`
with `{current bookmark}`.

So, how about half a plan:
1. add code to enable hookable suggestions for `to abort`
2. someone should survey the hg world to figure out what other things
might be wanted beyond `hg up -C .` and `hg up -C {currentbookmark}`
3. we review the current `to continue`
4. we look at wiring `hg continue` and `hg abort`