On Thu, Sep 18, 2008 at 5:43 PM, Trent W. Buck <[EMAIL PROTECTED]> wrote: > > I care about correct handling of ^D, particularly because of the > following use case: > > In Emacs' directory editor (dired), I put the cursor over a modified > file, type ! (to run a command on the selected file), and then type > > darcs rec -m Typo. > > instead of > > darcs rec -am Typo. > > Generally this happens when I'm bouncing between VCSs, because some > other VCSs just imply -a. > > Importantly, the dired-do-shell-command function of Emacs connects the > shell's input to /dev/null, and all of Emacs blocks until the command > terminates. If ^D isn't handled correctly and just loops forever, the > result is 100% CPU usage and a hung Emacs until I realize something is > wrong and terminate the process. > > I don't remember if darcs currently has this problem; I noticed it > recently with either unzip or unrar-nonfree. With darcs 2.0.2 on > Debian, both of these commands hang forever with 0% CPU, where foo is a > file with unrecorded changes: > > darcs rec </dev/null foo > darcs rec <. foo >
The patch I sent earlier today should fix this: http://lists.osuosl.org/pipermail/darcs-users/2008-September/013854.html And thanks for explaining your use case; it hadn't occurred to me that ^D handling could come up in such a situation, and emphasizes the importance of getting this behavior right. -Judah _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
