[darcs-users] Haskeline 0.3.2 doesn't work for twb.

Trent W. Buck trentbuck at gmail.com
Mon Dec 8 00:40:15 UTC 2008


Just a quick note, because I'm work-working.  Judah, I'll answer your
questions later.

On Sun, Dec 07, 2008 at 08:38:12AM -0800, Judah Jacobson wrote:
> On Sun, Dec 7, 2008 at 1:08 AM, Trent W. Buck <trentbuck at gmail.com> wrote:
> > It still doesn't work:
> >
> >  $ dist/build/darcs/darcs rec
> >  hunk ./src/Darcs/Commands/Tag.lhs 80
> >  +
> >  Shall I record this change? (1/1)  [ynWsfvpxdaqjk], or ? for help: y
> >  What is the patch name? foo^B^[[D^A^K^Cdarcs: interrupted
> >  $
> >
> > Worse, when I hit ^C above, it leaves _darcs/lock lying around, because
> > if I re-run the command
> >
> >  $ dist/build/darcs/darcs rec
> >  Waiting for lock /home/twb/VCS/darcs-illiterate/_darcs/lock
> >  Couldn't get lock /home/twb/VCS/darcs-illiterate/_darcs/lock
> >
> > This lockfile isn't left around if I use darcs 2.1.0, built without
> > haskeline:
> >
> >  $ darcs rec
> >  hunk ./src/Darcs/Commands/Tag.lhs 80
> >  +
> >  Shall I record this change? (1/1)  [ynWsfvpxdaqjk], or ? for help: y
> >  withSignalsHandled: Interrupted!D^A^K^C
> >
> >  $
> >
> > I also notice that colour isn't working in the with-haskeline version.

These problems are all gone if I build with make instead of cabal, so
I guess this is a cabal problem.


More information about the darcs-users mailing list