From mboxrd@z Thu Jan  1 00:00:00 1970
From: dexen deVries <dexen.devries@gmail.com>
To: picolisp@software-lab.de, 9fans@9fans.net
Date: Fri, 28 Sep 2012 15:09:26 +0200
Message-ID: <4028526.kJK0hItHXD@coil>
User-Agent: KMail/4.9 (Linux/3.6.0-rc4-l46; KDE/4.9.0; x86_64; ; )
In-Reply-To: <20120928112857.GA29306@software-lab.de>
References: <20120928112857.GA29306@software-lab.de>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Subject: Re: [9fans] Running PicoLisp in Acme
Topicbox-Message-UUID: bbd4847e-ead7-11e9-9d60-3106f5b1d025

Hi lists,

On Friday 28 of September 2012 13:28:57 you wrote:
> > Acme does not emulate anything resembling ANSI terminal. As far as =
I know,
> > it only treats TAB and LF characters in special way. In particular,=
 no
> > cursor addressing resembling anything of ANSI terminal.
>=20
> Yes, but this is on a level higher. The picolisp line editor avoids a=
ny
> dependence on terminal control sequences (termcap or terminfo), by
> relying solely on spaces and backspaces to format the line.


I see now. I have similar annoyance with Git -- which uses ^H (or was i=
t CR?)=20
to over-write line of text when indicating pull progress (1% ^H^H2% ^H^=
H^3%=20
etc.etc.).


> In any way, instead of completely disabling 'led', you might change t=
he
> function 'chgLine' in "lib/led.l", and replace "^H" ((prin "^H") in
> three places) with some other character which is suitable for acme.


I believe there's no direct replacement, but let's ask the nice folks o=
n=20
9fans@9fans.net -- I'm cross-posting this message.

--=20
dexen deVries

[[[=E2=86=93][=E2=86=92]]]