From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: skaller@ozemail.com.au, caml-list@inria.fr
Subject: Re: [Caml-list] Caml toplevel and readline
Date: Tue, 19 Jun 2001 12:10:57 +0200 [thread overview]
Message-ID: <20010619121057.B24428@lambda.u-strasbg.fr> (raw)
In-Reply-To: <20010619103908W.garrigue@kurims.kyoto-u.ac.jp>
On Tue, Jun 19, 2001 at 10:39:08AM +0900, Jacques Garrigue wrote:
> > Alternatively, why not build the toplevel
> > with ledit?
>
> I suppose that most people at INRIA are already using it with ledit,
> so they didn't think of including it. Also, ledit requires libunix,
> but I don't know if the terminal capacities included in ocamlrun
> would be enough in this case. The way it works currently, you probably
> need pipes. But all this should be solvable.
And ledit needs camlp4, right, but i gues syou could preprocess it or
something like that ?
> > > But the first man making a custom toplevel is dead:
> > > having both in the same file won't do.
> >
> > I am the one linking it into the toplevel, not INRIA.
> > It will have no impact on me, since I do not use the top
> > level for producing code (only for testing the occasional
> > small fragments).
>
> The standard distribution already contains a labltk toplevel, linked
> in custom mode. And INRIA distributes binaries.
But they could distribute them without libreadline being used.
Sure this would mean more work, but i think if someone contribute a patch for
supporting it, they would gladly accept it.
That said adding ledit or something similar to ocaml would be nice.
Did not some incarnation of caml-light had some kind of librealine like
functionality ? what happened to that ?
Or was it just librealine and it was removed, because of the licensing issue ?
Friendly,
Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-06-19 10:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 16:37 John Max Skaller
2001-06-14 6:40 ` Mark Wotton
2001-06-14 6:45 ` Jacques Garrigue
2001-06-14 10:32 ` leary
2001-06-14 15:47 ` Brian Rogoff
2001-06-14 19:43 ` John Max Skaller
2001-06-14 21:03 ` Pierre Weis
2001-06-15 5:05 ` leary
2001-06-15 10:21 ` Daniel de Rauglaudre
2001-06-15 20:59 ` John Max Skaller
2001-06-15 21:10 ` [Caml-list] Big_num not documented in manual John Max Skaller
2001-06-15 9:13 ` [Caml-list] Caml toplevel and readline Alan Schmitt
2001-06-15 14:12 ` Brian Rogoff
2001-06-15 9:34 ` Sven LUTHER
2001-06-16 17:46 ` leary
2001-06-18 7:32 ` Xavier Leroy
2001-06-18 9:48 ` Jacques Garrigue
2001-06-18 16:34 ` John Max Skaller
2001-06-19 1:39 ` Jacques Garrigue
2001-06-19 10:10 ` Sven LUTHER [this message]
2001-06-19 10:06 ` Sven LUTHER
[not found] ` <9gnrcd$4bv$1@qrnik.zagroda>
2001-06-21 6:05 ` Marcin 'Qrczak' Kowalczyk
2001-06-21 6:40 ` leary
2001-06-21 7:01 ` Jacques Garrigue
2001-06-22 14:56 ` Sven LUTHER
2001-06-22 15:36 ` Brian Rogoff
2001-06-24 20:59 ` Sven LUTHER
2001-06-22 17:52 ` Daniel de Rauglaudre
2001-06-13 20:37 [Caml-list] Repeat: is there a Qt binding for OCaml? Adriaan de Groot
2001-06-14 6:57 ` Jacques Garrigue
2001-06-14 7:51 ` leary
2001-06-14 8:36 ` [Caml-list] Caml toplevel and readline Jacques Garrigue
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=20010619121057.B24428@lambda.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=skaller@ozemail.com.au \
/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;
as well as URLs for NNTP newsgroup(s).