[Gterm-discuss] "ls" bug

[Timothy M. <th...@ya...>]

I'm working on debugging the terminal, and what I'm seeing is a bit
odd.  In the case where things get messed up, I just start the terminal
and do 'ls'.  I have the terminal producing debug output, where
non-printing characters are shown as \oct.  This is the debug output:

len=9,data:[sh-2.05# ]
len=1,data:[l]
len=1,data:[s]
len=2,data:[\015\012]
len=61,data:[actions.cpp  Makefile\011\011 pseudo_openpty.hpp 
vt52_states.cpp\015\012]
len=65,data:[actions.o    Makefile.config\011 pseudo_unix98.cpp  
vt52_states.o\015\012]
len=58,data:[CVS\011     Makefile.depend\011 pseudo_unix98.hpp  
xintfc.cpp\015\012]
len=56,data:[gterm\011     pseudo_classic.cpp  README\011\011    
xintfc.doc\015\012]
len=59,data:[gterm.cpp    pseudo_classic.hpp  setupcvs\011    
xintfc.hpp\015\012]
len=52,data:[gterm.doc    pseudo.cpp\011\011 states.cpp\011    
xintfc.o\015\012]
len=51,data:[gterm.hpp    pseudo.hpp\011\011 states.o\011    
xkeys.cpp\015\012]
len=48,data:[gterm.o      pseudo.o\011\011 utils.cpp\011    
xkeys.o\015\012]
len=42,data:[libgterm.a   pseudo_openpty.cpp  utils.o\015\012]
len=9,data:[sh-2.05# ]


In the lines that are messed up, there is \011, which is tab.

Now, the first thing I tried to do in order to debug was to capture
what was coming out of ls, so I did "script /tmp/q".  But when I did
that, I got correct output on the screen:

len=1,data:[l]
len=1,data:[s]
len=2,data:[\015\012]
len=977,data:[\033[00m\033[00mactions.cpp\033[00m 
\033[00mMakefile\033[00m            \033[00mpseudo_openpty.hpp\033[00m 
\033[00mvt52_states.cpp\033[00m\015\012\033[00mactions.o\033[00m   
\033[00mMakefile.config\033[00m     \033[00mpseudo_unix98.cpp\033[00m  
\033[00mvt52_states.o\033[00m\015\012\033[01;34mCVS\033[00m         
\033[00mMakefile.depend\033[00m     \033[00mpseudo_unix98.hpp\033[00m  
\033[00mxintfc.cpp\033[00m\015\012\033[01;32mgterm\033[00m       
\033[00mpseudo_classic.cpp\033[00m  \033[00mREADME\033[00m             
\033[00mxintfc.doc\033[00m\015\012\033[00mgterm.cpp\033[00m   
\033[00mpseudo_classic.hpp\033[00m  \033[00msetupcvs\033[00m           
\033[00mxintfc.hpp\033[00m\015\012\033[00mgterm.doc\033[00m   
\033[00mpseudo.cpp\033[00m          \033[00mstates.cpp\033[00m         
\033[00mxintfc.o\033[00m\015\012\033[00mgterm.hpp\033[00m   
\033[00mpseudo.hpp\033[00m          \033[00mstates.o\033[00m           
\033[00mxkeys.cpp\033[00m\015\012\033[00mgterm.o\033[00m     
\033[00mpseudo.o\033[00m            \033[00mutils.cpp\033[00m          
\033[00mxkeys.o\033[00m\015\012\033[00mlibgterm.a\033[00m  
\033[00mpseudo_openpty.cpp\033[00m 
\033[00mutils.o\033[00m\015\012\033[m\033]0;tim@puck:/software/users/tim/gterm/GTermRoot\007]
len=23,data:[[root@puck GTermRoot]# ]
len=1,data:[e]
len=1,data:[x]
len=1,data:[i]
len=1,data:[t]
len=29,data:[Script done, file is /tmp/q\015\012]
len=9,data:[sh-2.05# ]

Additionally, if, in the shell where 'ls' causes incorrect output, I
were to cat /tmp/q, I get correct output on the screen.

It must be some problem with the environment, but I can't figure it
out.

Also, I notice that in all cases, if I run Lynx, it looks completely
wrong, although it looks fine in other terminals.  Lines that should
look like they have CR/LF looks like they're only getting LF, so
they're  spiralling around the screen.  The code between lines that I
find is: \012\033[4G

I will investigate further.


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com