Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!rutgers!att!cbnewsl!flh
From: flh@cbnewsl.att.com (frederick.l.horman..iii)
Newsgroups: comp.windows.x
Subject: new escape sequences for xterm
Keywords: xterm, ANSI, curses
Message-ID: <1990May9.212526.5448@cbnewsl.att.com>
Date: 9 May 90 21:25:26 GMT
Organization: AT&T Bell Laboratories
Lines: 33


The following problem was recently noted by an AT&T customer:

	The AT&T xterm recognizes some escape sequences that
	are not recognized by the MIT xterm.  In particular,
	two escape sequences were added to signal when a
	program enters/exits curses mode so that xterm can
	inhibit window resizing while in curses mode.  As a result,
	someone trying to rlogin to an SVR4 system (where
	the AT&T xterm has been installed -- with its terminfo
	entry) will get extraneous output when running a curses
	program. 

We (AT&T) would like to donate the added functionality to MIT, so
that the MIT xterm will recognize the escape sequences and behave
appropriately.  To do this with minimal change, I need to pick
a set of escape sequences to be used for the smcup/rmcup terminfo
capabilities which are used to signal enter/leave curses mode.

I have tentatively chosen to use the \E[< and \E[> sequences because
they are designated by ANSI for private use and are not currently
used by the MIT and AT&T xterms.  I would like feedback on this
choice of escape sequences.

If you see a conflict that I'm missing, please let me know.  Feel
free to respond to this newsgroup or directly to me.


Thanks,

Fred Horman
AT&T
flh@attunix.att.com