unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ivan Kanis <expire-by-2009-10-21@kanis.fr>
Cc: Emacs Sources <gnu-emacs-sources@gnu.org>,
	emacs devel <emacs-devel@gnu.org>
Subject: Re: nterm a vt100 emulator
Date: Mon, 19 Oct 2009 22:10:57 -0400	[thread overview]
Message-ID: <jwvr5syq0ne.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87skdjrgqb.fsf@kanis.fr> (Ivan Kanis's message of "Fri, 16 Oct 2009 08:32:44 +0200")

>> Could you expand a bit on it?  Mostly, how does it compare to term.el
>> and terminal.el?

> Hi Stefan,

> I wrote it because I couldn't fix the cursor bug in term.

That was my guess as well ;-)

> 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.

> I can't comment on terminal, I haven't used it.

Neither have I.  Has someone used it?  Should we move it to `lisp/obsolete'?

> Things that remains to do:
> - Double width character
> - Double height character
> - Sanitize keyboard map
> - ANSI color
> - VT52 compatibility mode

Does it adapt to a window's size or does it have a fixed size
independent from the window where the buffer is displayed?

> I think nterm is easier to maintain than term.  One look at term's
> term-emulate-terminal function should convince anyone that term cannot
> be maintained anymore.  Compare with nterm equivalent function
> nterm-emulate it is only 25 lines long.

term.el's maintainability is indeed a problem.


        Stefan




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

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=jwvr5syq0ne.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=expire-by-2009-10-21@kanis.fr \
    --cc=gnu-emacs-sources@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 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).