caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anthony Tavener <anthony.tavener@gmail.com>
To: rixed@happyleptic.org
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml top-level line editing script
Date: Wed, 4 Jul 2012 15:19:11 -0600	[thread overview]
Message-ID: <CAN=ouMQcdMeT75PD+fd6Hq=WTYw-Ldkt=WZ0BdEyoUd5Tsci7A@mail.gmail.com> (raw)
In-Reply-To: <20120704182415.GB7341@yeeloong>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

Oh geez... I've only been using: alias ocaml='rlwrap ocaml'. I didn't RTFM
on rlwrap.

A colored prompt helps, and multi-line edit! Thanks! I'll leave -rectypes
as a default for crazy people though. ;)


On Wed, Jul 4, 2012 at 12:24 PM, <rixed@happyleptic.org> wrote:

> Interresting, although rlwrap gives you history, filename completion,
> prompt coloring, syntax completion, brackets matching, use of an
> external editor and easy configuration via .inputrc.
>
> For instance I have this in my .zshrc:
>
> alias ocaml='rlwrap --prompt-colour=green --multi-line --remember
> --complete-filenames --command-name=ocaml ocaml -rectypes'
>
> And this in my .inputrc:
>
> $if ocaml
>     "\C-o": "()\C-b"
>     "\C-n": ";;\n"
> $endif
>
> While the default C-^ launches vi (for multi-line edits)
>
> I'm confident others have much more gorgeous inputrcs, though. Please
> share :-)
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>

[-- Attachment #2: Type: text/html, Size: 1841 bytes --]

      reply	other threads:[~2012-07-04 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 17:06 Aaron Bohannon
2012-07-04 17:56 ` "Markus W. Weißmann"
2012-07-05  1:46   ` Aaron Bohannon
2012-07-05  4:25     ` Aaron Bohannon
2012-07-04 18:24 ` rixed
2012-07-04 21:19   ` Anthony Tavener [this message]

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='CAN=ouMQcdMeT75PD+fd6Hq=WTYw-Ldkt=WZ0BdEyoUd5Tsci7A@mail.gmail.com' \
    --to=anthony.tavener@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=rixed@happyleptic.org \
    /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).