Ubuntu 8.04, gnome-terminal 2.22.1-0ubuntu2, libvte9 1:0.16.13-1ubuntu1.
Using tput(1) to send the terminal's terminfo init string to
gnome-terminal, and hence vte as I understand it, gives inconsistent
results. It often fails to initialise the terminal back to its
defaults.
Here's a command to show the desired behaviour.
tr \\0 \\012 </dev/zero | head -100 |
while read f; do tput setf 4; printf X; tput setf 0; printf Y; done
It gives an alternating sequence of red X's and black Y's. Replacing
the `setf 0', which is setting the foreground colour to black, with
`init', as in
tr \\0 \\012 </dev/zero | head -100 |
while read f; do tput setf 4; printf X; tput init; printf Y; done
gives many red Y's, i.e. the `tput init' is *sometimes* failing to have
effect. I suspect it's a subtle timing issue where vte is examining the
time between characters in escape sequences to determine if they are, in
fact, an escape *sequence*.
Note, xterm(1), and other terminal emulators I've tried, give consistent
results, the `tput init' is always interpreted the same way.
Here's a couple of bits of information that may be useful to confirm it
isn't something odd on my local setup.
$ echo $TERM
xterm
$ tput init | od -c
0000000 033 [ ! p 033 [ ? 3 ; 4 l 033 [ 4 l 033
0000020 >
0000021
$
This bug causes legacy programs that work consistently on other Unix and
Linux systems to have display glitches with varying impact depending on
when vte decides not to honour the request. The red/black XYs is just
my simplification. :-)
do you get the same with vte 0.17 available on intrepid?