all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: Ivan Kanis <expire-by-2009-10-20@kanis.fr>,
	emacs devel <emacs-devel@gnu.org>
Subject: Re: nterm a vt100 emulator
Date: Fri, 16 Oct 2009 00:21:24 -0700 (PDT)	[thread overview]
Message-ID: <200910160721.n9G7LO1h012843@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87d44oqlbf.fsf@catnip.gol.com> (Miles Bader's message of "Fri, 16 Oct 2009 08:39:00 +0900")

Miles Bader <miles@gnu.org> writes:

  > Ivan Kanis <expire-by-2009-10-20@kanis.fr> writes:
  > > This a vt100 emulator for emacs. It has a lot of rough edges. As it
  > > stands it passes the first 3 tests of vttest. I have another project
  > > coming up so I won't be able to work on nterm for a while.
  > >
  > > http://kanis.fr/nterm.html
  > 
  > We've already got two different terminal emulators in Emacs (with
  > completely separate code bases); do we really want a third...?

IMO a third one could be considered as a replacement for term.el (never
seen terminal.el).   But only if it's actively maintained.

term.el is not very maintainable, some bugs are quite hard to fix.

Also nterm.el seems to be trying to emulate vt100.  Nowadays all
terminal emulators try to emulate xterm, which is the de facto standard...




      reply	other threads:[~2009-10-16  7:21 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
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 [this message]

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=200910160721.n9G7LO1h012843@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=expire-by-2009-10-20@kanis.fr \
    --cc=miles@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.