From: storm@cua.dk (Kim F. Storm)
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Miles Bader <miles.bader@necel.com>, emacs-devel@gnu.org
Subject: Re: [dalias@aerifal.cx: ansi-term \e[J causes spurious newline [revised report]]
Date: Thu, 22 Mar 2007 10:27:00 +0100 [thread overview]
Message-ID: <m3wt198w7v.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <200703220508.l2M58fte023654@oogie-boogie.ics.uci.edu> (Dan Nicolaescu's message of "Wed\, 21 Mar 2007 22\:08\:41 -0700")
Dan Nicolaescu <dann@ics.uci.edu> 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
does.
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
before.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2007-03-22 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 18:10 [dalias@aerifal.cx: ansi-term \e[J causes spurious newline [revised report]] Richard Stallman
2007-03-21 16:51 ` Chong Yidong
2007-03-21 18:40 ` Dan Nicolaescu
2007-03-21 19:16 ` Chong Yidong
2007-03-21 20:16 ` Dan Nicolaescu
2007-03-22 2:36 ` Miles Bader
2007-03-22 3:22 ` Dan Nicolaescu
2007-03-22 3:44 ` Miles Bader
2007-03-22 5:08 ` Dan Nicolaescu
2007-03-22 6:08 ` Miles Bader
2007-03-22 9:27 ` Kim F. Storm [this message]
2007-03-22 17:06 ` Dan Nicolaescu
2007-03-22 22:00 ` Kim F. Storm
2007-03-22 5:01 ` Richard Stallman
2007-08-03 15:49 ` Dan Nicolaescu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wt198w7v.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=miles.bader@necel.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).