Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!bloom-beacon!dont-send-mail-to-path-lines
From: gildea@expo.lcs.mit.EDU (Stephen Gildea)
Newsgroups: comp.windows.x
Subject: Re: xterm -- how can I disable screen restore?
Message-ID: <9104181754.AA00842@alex.lcs.mit.edu>
Date: 18 Apr 91 17:54:02 GMT
References: <1047@redford.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 16


    >Why doesn't titeInhibit simply make xterm ignore these control
    >sequences?
    It does.  I use it to ignore it for more.  It doesn't work for vi
    because, as you have pointed out (In text which I deleted) vi reads the
    terminfo database directly, and forces a screen save.  

No, it doesn't.  titeInhibit removes the ti and te entries from the
termcap entry, but xterm still obeys them if they get sent anyway.
That's why it doesn't work for SunOS vi; it doesn't use termcap, so
still knows how to send ti and te.

Now, to answer the original question, Why?  Answer: it's a bug.

 < Stephen
   MIT X Consortium