>> On the mac (darcs 2.1.2): applying these patches interactively, or 
>> pulling them, or obliterating them one at a time, hangs doing seemingly 
>> nothing after the first y or n. However I can non-interactively apply 
>> them, and obliterate --last 6 -a also works.

I see this hang-after-a-prompt in other cases too, like darcs send -O. 
I'm pretty sure this is just a ui bug and suspect something haskeline 
related. There are two 2.1.2 mac binaries on the download page; exrae's 
shows the bug and fivesquare's does not. I hope this helps.

I tried but wasn't able to replicate this issue with exrae's darcs-2.1.2. (I'm also 
using Terminal.app on Leopard.)

To attempt to reproduce, I used 'darcs get' to copy my existing local repo of 
darcs.net; then in the copy I unrecorded/reverted 10 patches interactively, and was 
able to apply them back interactively; both the single character y/n reading and 
whole line input worked fine.  Can you give more specific instructions on how to 
reproduce this issue?  

Also, I'm pretty sure that the binary in question was built without haskeline 
support, since the UI does not recognize arrow keys and the binary doesn't read my 
~/.haskeline file.  (Recall that in 2.1.2, the haskeline cabal flag was set to false 
by default.)

Tonight, I'm not able to reproduce it either. :( But I'm not  
delusional... I swear...

Thank you Judah. I'll close and pipe up if it happens again.

It happened again. darcs 2.1.2, 2.2, and unstable builds made yesterday on my linux 
server all hang with a number of commands, while an older 2.1.98.x on my mac does 
not. This is the same symptom as issue1050 (also keep an eye on issue0342). I see it 
with both make and cabal builds on that machine. They are not built with the 
haskeline flag and I don't have that installed. I can't see what exactly is going on.

The hang described on this page shows no cpu usage by the way. Also, the same 
darcs built with ghc 6.8 on this machine does not hang.

Pulling the patch "Make Haskeline a required dependency." (and the subsequent 
conflict resolution) has fixed this problem in my darcs builds (ghc 6.10.1, 
gnu/linux, x86_64). I also upgraded haskeline as required by latest darcs (from 
0.6.0.1 to 0.6.1.2). That alone didn't fix it, but I thought I'd mention it.

Whatever it was, I'm happy to be able to run latest darcs again on that machine.