On Wed, Dec 17, 2008 at 6:55 PM, Trent W. Buck <[email protected]> wrote:
>
> Can it read my ~/.inputrc yet? ;-)
> I'm awfully fond of
>
>    $if mode=emacs
>      # poor-man's insert-parentheses
>      (: "\C-v(\C-v)\C-b"
>      [: "\C-v[\C-v]\C-b"
>      {: "\C-v{\C-v}\C-b"
>      }: forward-char
>      ]: forward-char
>      ): forward-char
>    $endif

As of 0.5.0.1, you can do that: (although not with the exact .inputrc
notation :-)
http://trac.haskell.org/haskeline/wiki/CustomKeyBindings

Thanks for the suggestion!

>> It might be worth bumping up the dependency to haskeline-0.5 for
>> darcs-2.2; it could use a little more testing, but no code changes
>> would be necessary since the part of the API that darcs uses has
>> stayed the same.  I'll send a patch/proposal once the testing/bugfixes
>> are completed.
>
> Is there any reason it won't work with 0.4?  Why not just increase the
> ceiling (>= 0.4 && <= 0.5), rather than the floor as well (== 0.5)?
> That's what I get told to do for Debian package dependencies, because it
> makes it easier to "backport" (i.e. cherry pick) new upstream of a
> critical package into an otherwise stable OS.
>
> (Easier because the backporter doesn't have to override the dependency,
> nor backport extra library packages.)

The only issue I can think of is that people building with 0.3.* or
0.4.* might miss out on some haskeline bug fixes (such as the encoding
issue mentioned a few days ago).  But probably that's fine since the
common use case "cabal install darcs" will update haskeline to the
latest version anyway.

-Judah
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users

Reply via email to