1 |
As soon as some textmode applications in xterm stop, their output gets |
2 |
wiped, and the xterm screen is restored to what it looked like before I |
3 |
launched the app. Somebody thought they were being "helpful"; then |
4 |
again, so did the designers of "Clippy". I don't know how many updates |
5 |
ago the behaviour changed, but here's what happens... |
6 |
|
7 |
Let's say I'm having a problem with packet loss to/from a certain |
8 |
internet server. I would run "mtr" which gives an ongoing enhanced |
9 |
traceroute display. When it gets to the router that's dropping packets |
10 |
I would hit "Q" and mtr quits. |
11 |
|
12 |
Before the update |
13 |
================= |
14 |
I would copy/paste the mtr output into an email, and send it off to |
15 |
whomever, with the output showing the packet-loss stats. |
16 |
|
17 |
After the update |
18 |
================ |
19 |
As soon as mtr quits, its output gets wiped, and the xterm screen is |
20 |
restored to the state it was in before mtr was launched... helpful NOT! |
21 |
|
22 |
I've discovered that I can suspend it with {CTRL-S}, but I shouldn't |
23 |
have to resort to that. Using Google, I found references to |
24 |
"man termcap", which stated that this behaviour was controlled by |
25 |
entries in /etc/termcap. Despite the fact that I have the termcap man |
26 |
page on my system, I do *NOT* have /etc/termcap. Does anyone have a |
27 |
sample /etc/termcap (or will ~/.termcap work?) to stop the screen |
28 |
restore after a text application quits? |
29 |
|
30 |
-- |
31 |
Walter Dnes <waltdnes@××××××××.org> |