From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [dalias@aerifal.cx: ansi-term \e[J causes spurious newline [revised report]]
Date: Wed, 21 Mar 2007 13:16:50 -0700 [thread overview]
Message-ID: <200703212016.l2LKGo67015610@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <87ps724dbd.fsf@stupidchicken.com> (Chong Yidong's message of "Wed\, 21 Mar 2007 15\:16\:38 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> > > > echo -e 'hello\e[Jworld'
> > > >
> > > > On a vt100/ansi/ecma compatible terminal, this should leave
> > > > "helloworld" visible on the screen, with everything afterward cleared.
> > > > On GNU emacs' ansi-term, it prints hello on one line and world on the
> > > > next, after clearing to the end of the screen.
> >
> > In general tests using "echo" are not good enough, the correct way to
> > do it is to use "tput", there are some subtleties involved...
>
> On the other hand, using "echo" in ansi-term does produce a different
> result from doing it in xterm. Isn't that divergent behavior?
It different behavior for undefined behavior, so it's fine.
next prev parent reply other threads:[~2007-03-21 20:16 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200703212016.l2LKGo67015610@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.