From: "Sébastien Dailly" <sebastien@chimrod.com>
To: Martin DeMello <martindemello@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ledit not handling home/end sequences properly
Date: Wed, 2 Oct 2013 10:39:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1310021037420.9415@goku.chimrod.com> (raw)
In-Reply-To: <CAFrFfuFPh8x3t0M2YTLSbpp5Q0_Tnx48pLCk8F=Qd8TMQ=2Y4A@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 395 bytes --]
On Wed, 2 Oct 2013, Martin DeMello wrote:
> Want to check before sending the patch in - can anyone reproduce this
> issue, or is it some peculiarity of my setup?
>
> I needed to add the following patch to ledit-2.0.3 to get home/end
> handled properly on terminals other than xterm:
I've the same problem with ledit. This is the reason why I switched to
rlwrap wich works fine.
--
Sébastien
next prev parent reply other threads:[~2013-10-02 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 8:20 Martin DeMello
2013-10-02 8:39 ` Sébastien Dailly [this message]
2013-10-02 8:48 ` Daniel de Rauglaudre
2013-10-02 19:51 ` Martin DeMello
2013-10-08 9:41 ` Daniel de Rauglaudre
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=alpine.DEB.2.10.1310021037420.9415@goku.chimrod.com \
--to=sebastien@chimrod.com \
--cc=caml-list@inria.fr \
--cc=martindemello@gmail.com \
/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