It's not clear to me what "darcs whatsnew -i" would do. Clearly spelling out the
spec for it will make it easier for someone to implement.

Presumably Zooko wants something that lets users step through primitive patches
in the same way record -i does.

I can only imagine these commands right now:

  s: skip changes to this file

  v: view this change in full
  p: view this change in full with pager
  x: view a summary of this change

  q: quit whatsnew

  j: skip to next change
  k: back up to previous change

I guess whoever decides to implement this can work out the UI

Agreed. : - ) I would like that. (And I agree with ProbablyEasy, too.)

I missed this feature just now, so here is my +1.

I am working on this atm. Right now I think I got most of the machinery
in place.

I have a UI question though, 
how do you see the prompt? Should it display a hunk and display a hunk
in a context when the user presses 'y'?

And, Eric, what do you mean by a "summary of this change"?

I've pushed the necessary patches to my darcshub mirror:

- http://hub.darcs.net/co-dan/darcs-screened/patch/20140203213836-e7f45
- http://hub.darcs.net/co-dan/darcs-screened/patch/20140204070539-e7f45

Sorry everyone, I changed the patches a little bit. The newest version
can be found at the darcsden:
http://hub.darcs.net/co-dan/darcs-screened/changes

I also sent a patch bundle via `darcs send'

Attachments

• issue851.dpatch

The changes have been merged into -screened

The following patch sent by Dan Frumin <difrumin@gmail.com> updated issue issue851 with
status=resolved;resolvedin=2.10.0 HEAD

* resolve issue851: interactive mode for whatsnew 
Ignore-this: 898f8e458fa5d135fc9a4307422fe039