unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Ivan Kanis <expire-by-2009-10-25@kanis.fr>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs devel <emacs-devel@gnu.org>
Subject: Re: nterm a vt100 emulator
Date: Tue, 20 Oct 2009 11:49:46 -0700 (PDT)	[thread overview]
Message-ID: <200910201849.n9KInkR2028827@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87ljj6zl8t.fsf@kanis.fr> (Ivan Kanis's message of "Tue, 20 Oct 2009 07:29:22 +0200")

Ivan Kanis <expire-by-2009-10-25@kanis.fr> writes:

  > Stefan Monnier <monnier@iro.umontreal.ca> wrote:
  > 
  > >> term and terminal are not meant to be full emulation.  term has
  > >> a pager and line mode which nterm doesn't do.  nterm doesn't track
  > >> current directory like term does.
  > >
  > > That makes it sound like nterm is like term but with less features.
  > > I'm sure there's an upside to it.  Also, if you could explain how these
  > > different design decisions affect the ability to fix the original cursor
  > > bug, that would be great.
  > 
  > The recorder takes a trace of characters received by the
  > terminal. Someone can easily reproduce a bug by replaying the trace
  > both on xterm and nterm. I don't think term has that feature.

See term-start-output-log





  reply	other threads:[~2009-10-20 18:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 14:45 nterm a vt100 emulator Ivan Kanis
2009-10-15 20:11 ` Stefan Monnier
2009-10-16  6:32   ` Ivan Kanis
2009-10-20  2:10     ` Stefan Monnier
2009-10-20  3:37       ` Miles Bader
2009-10-20  5:29       ` Ivan Kanis
2009-10-20 18:49         ` Dan Nicolaescu [this message]
2009-10-21  5:12           ` Ivan Kanis
2009-10-21  5:52             ` Dan Nicolaescu
2009-10-15 23:39 ` Miles Bader
2009-10-16  7:21   ` 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=200910201849.n9KInkR2028827@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=expire-by-2009-10-25@kanis.fr \
    --cc=monnier@iro.umontreal.ca \
    /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).