From: Richard Jones <rich@annexia.org>
To: Fabrice Marchant <fabricemarchant@free.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Customising ledit commands ?
Date: Wed, 6 Dec 2006 13:15:50 +0000 [thread overview]
Message-ID: <20061206131550.GA32664@furbychan.cocan.org> (raw)
In-Reply-To: <20061206111052.4f08441c.fabricemarchant@free.fr>
On Wed, Dec 06, 2006 at 11:10:52AM +0100, Fabrice Marchant wrote:
> Please is it possible to change the behaviour of ledit ( without editing its source ) this way :
[...]
Not a direct answer to your question, but you could always try rlwrap.
It works in much the same way as ledit, and uses readline so it can be
customised using ~/.inputrc (see readline(3) for instructions on how
to configure that file).
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Internet Marketing and AdWords courses - http://merjis.com/courses - NEW!
Merjis blog - http://blog.merjis.com - NEW!
prev parent reply other threads:[~2006-12-06 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 10:10 Fabrice Marchant
2006-12-06 13:15 ` Richard Jones [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=20061206131550.GA32664@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=fabricemarchant@free.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