From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Readline Support for REPL
Date: Mon, 10 Aug 2015 12:27:04 +0200 [thread overview]
Message-ID: <20150810122704.Horde.g5szeLPSqlBSfVGXiKyZSw1@webmail.in-berlin.de> (raw)
In-Reply-To: <CAPFanBEwEJpWDyTs0piuT3Xh144qA2P7hrmFWmjuJLa4pHOUrw@mail.gmail.com>
...there also is "ledit" as support for the toplevel-usage.
Maybe utop is what I could try also...
Zitat von Gabriel Scherer <gabriel.scherer@gmail.com> (Mon, 10 Aug
2015 11:24:15 +0200)
> Note that utop already provides these features and much more:
> https://github.com/diml/utop
>
> I'm not sure improving the toplevel is a good investment of your efforts,
> given that there exists such a nice alternative, and that the switching
> costs are basically zero for toplevels.
>
> On Mon, Aug 10, 2015 at 1:37 AM, Dhaivat Pandya <dhaivatpandya@gmail.com>
> wrote:
>
>> Hi,
>>
>> I was wondering if readline support for the OCaml toplevel would be
>> appreciated. I understand that running the repl with "rlwrap" solves a
>> similar problem but if we were to implement readline support, we may later
>> on build on it with tab-completion, etc.
>>
>> If it is needed, I would be glad to implement support.
>>
>> -
>> Dhaivat
>>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2015-08-10 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 23:37 Dhaivat Pandya
2015-08-10 9:20 ` Ralf Treinen
2015-08-10 9:24 ` Gabriel Scherer
2015-08-10 10:27 ` Oliver Bandel [this message]
2015-08-10 15:01 ` Dhaivat Pandya
2015-08-10 15:50 ` Francois Berenger
[not found] <20150811100018.8AA337EF27@sympa.inria.fr>
2015-08-11 10:15 ` Nils Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150810122704.Horde.g5szeLPSqlBSfVGXiKyZSw1@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox