I wish I could run "darcs push", and then when the interactive mode brings a
patch to my attention, I could obliterate that patch.  In a similar vein, 
I wish that I could run "darcs record", and then when the interactive mode
brings a hunk to my attention, I could revert that hunk.

Regards,

Zooko

> I wish I could run "darcs push", and then when the interactive mode brings a
> patch to my attention, I could obliterate that patch.  

I vote against this as being unnecessary and uncommon (at least for me). 

> In a similar vein, I wish that I could run "darcs record", and then when the
> interactive mode brings a hunk to my attention, I could revert that hunk.

On the other hand, I have wanted to do this frequently and share this wish. 
In the interactive record menu, "r" (for revert) is conveniently unused. 

It probably merits an extra confirmation as a destructive action.

MarkStos said this was uncommon (at least for him), but it is common for me.  It
just came up again.

I've done a few days worth of work, and now I want to split the work into
logically separate patches.  For example, the first patch will probably be the
test cases, separate from the changes to the code to make the code pass the new
tests.  So I run "darcs record" and start stepping through the files and hunks
looking for logically related changes that I can put into a single patch (see
also issue126).

Now I find a typo as one of the hunks.  I have to either cancel this "darcs
record" and go run "darcs revert" to destroy the typo, and then resume the
"darcs record" and reselect any hunks that I've already selected, or else I have
to remember that after I'm finished with this "darcs record" then I need to come
back and do a "darcs revert" and then step through the changes until I find this
typo again.

It would be perfect if there were a key I could press -- right now, while I'm in
the middle of a big interactive "darcs record" -- which would revert this typo.

> Now I find a typo as one of the hunks.  I have to either cancel this "darcs
> record" and go run "darcs revert" to destroy the typo, and then resume the
> "darcs record" and reselect any hunks that I've already selected, or else I have
> to remember that after I'm finished with this "darcs record" then I need to come
> back and do a "darcs revert" and then step through the changes until I find this
> typo again.
> 
> It would be perfect if there were a key I could press -- right now, while I'm in
> the middle of a big interactive "darcs record" -- which would revert this typo.

I haven't re-read what I said before, but I do sometimes run into the same
case.  As I'm recording, I find that I've left some debugging output in the
code. It would be nice to revert the debugging statements while I'm looking at
them during the 'record'.

    Mark

I think for reverting a hunk when recording, issue291 is good enough albeit not
quite the same.

While I see that is both useful and common, I think it's ultimately in
everybody's best interests if we applied the Keep-It-Simple-Stupid principle here.

We have to manage this delicate balance between being simple and featureful. 
Sometimes there is no trade-off and we can offer both at the same time.

I claim that this is one of those cases where a nice feature adds has an
unacceptable cost in simplicity (UI-wise).  OK, it's just another key-press to
offer, but all these tiny changes add up. Sorry Zooko, I'm going to resist this
change and recommend a wont-fix.  Discussion on darcs-users if you want to
re-open this.

I intend to copy the discussion for revert-upon-record to issue1734