[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address@hidden: ansi-term \e[J causes spurious newline [revised repo

From: Kim F. Storm
Subject: Re: address@hidden: ansi-term \e[J causes spurious newline [revised report]]
Date: Thu, 22 Mar 2007 10:27:00 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.96 (gnu/linux)

Dan Nicolaescu <address@hidden> writes:

> Well, that's a rat hole that I don't think we want to get into.  Not at
> this point in the release cycle. If users show that some features are
> required by real applications to run correctly, then we can consider
> it.

The reporter specifically mentioned busybox command line editing.

We cannot expect embedded systems to rely on termcap/terminfo.
Rather they will issue hardcoded VT100 escape sequences - like
ESC [ J, and expect the terminal emulator to DTRT...

I've tested the 'echo' example with both xterm and minicom (which I
use with embedded systems).  Both behave identically - for ESC [ J
and for ESC [ 1 J -- and in accordance with the reporter's expectations
for a "true" VT100 terminal.

So you may claim that the behaviour is "undefined" - but practical
tests shows "consistent" behaviour, different from what Emacs term

IMO, we should fix term to behave like other VT100 emulators.
The current behaviour is clearly broken -- besides, fixing this
doesn't change the semantics of the only case where it was defined

Kim F. Storm <address@hidden> http://www.cua.dk

reply via email to

[Prev in Thread] Current Thread [Next in Thread]