| From: Randy Carpenter <[EMAIL PROTECTED]>
| So instead of following a standard, you are choosing to be more compatible
| with possibly non-standard clients, and not support standard UNIX systems?
| You are adding fancy features to something that should be simple, and by
| doing so, breaking compatibility.
|
| That doesn't make sense. I say follow the standards, and let the
| non-standard clients be broken.
Hear, hear!
And futhermore, the non-standard clients are not even broken by this
reversion! I've done it myself, on each of my RH6.1 systems *and nothing
breaks*.
The right change is to improve the xterms, but leave the
tercap/terminfo databases the same until the new xterms are deployed
everywhere (10 years?). If you wish, add a new TERM name (xterm99?)
to exploit the new features.
Think of it this way: the xterm entry should describe all (X11)
xterms. If you change xterm incompatibly, give it a new name. In
fact, the change to the xterm program is upward compatible, so that is
fine. The change made to the xterm description is neither compatible
nor acceptable.
Hugh Redelmeier
[EMAIL PROTECTED] voice: +1 416 482-8253
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
