3/18 Can someone remind me what is required to prevent programs like
less, for example, from sending their output to a "separate" screen
that gets erased when the program is killed, as opposed to just on
the normal stdout terminal like, for example, ls? Thanks.
\_ you must not have taken e190 yet.
\_ ugh... typos corrected. I assume that's what you were talking
about? ...and by the way, I'm L&S CS.
\_ You passed Subject A?
\_ I passed out of it with my awesome AP English score.
boo-ya, bee-otch.
\_ Clearly the difficulty of the AP exam has declined in
recent years, "boo-ya, bee-otch".
\_ I took it in '96, biznatch. boo-fuckin-ya.
\_ Like I said. "... in recent years". Anything
from after the time they changed all the tests and
dumbed everything down so you could still get a
high score to preserve your precious self-esteem
without taking a double dose of prozac doesn't
count as a serious academic success.
\_ I was joking and you're a complete dweeb.
\_ Your best bet is less -X, although YMMV depending on your terminal's
termcap entry's quirks. -alexf
\_ if you use xterm, add this to your Xdefaults or wherever you
incant X resources: XTerm.VT100.titeInhibit: true
\_ It's all black cats and cast iron pots at midnight under a full
moon. |