era eriksson <[email protected]> writes: > Simon Marlow <marlowsd <at> gmail.com> writes: >> >>> darcssum has been broken for me since about darcs 2's release... once I >> >>> enter my commit message and type C-c C-c to submit it, "darcs rec ." is >> >>> run, and never exits. The _darcs/lock file stays around, and I have to >> >>> kill -15 the darcs process to use the repo again. > > Pardon this belated reply. Do you think you could examine the " *darcs > record*" > buffer and report back here? > > I have a half-finished private version which tries to code around some IMHO > problematic scenarios. Basically, the problem boils down to this: if Darcs > responds with something unexpected, darcsum will appear to hang. There are > probably many little things which can go wrong. At the very least, I think > darcsum should display any unexpected output so that you don't just sit there > waiting for it to finish when it never will.
Cool, I'll get around to this when I have a spare half-hour. Is your work on darcsum darcs-gettable? It'd be useful to add to my list of "neat stuff", even if it's in a draft state. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
