On Fri, Jul 21, 2006 at 03:13:28PM -0500, Michael Parson wrote:
>On Fri, Jul 21, 2006 at 03:13:03PM -0400, George Georgalis wrote:
>> I had posted this in the tech-pkg list (sorry)
>> assuming a package was missing or corrupted, but I
>> guess it is more of a netbsd-users, question...
>> 
>> I'm having a strange terminal problem within screen.
>> Apparently color control sequences are replaced by
>> "OOPS" eg 
>> 
>>  $ colorls -G / 
>> .cshrc  boot    OOPSetc     OOPSlib     OOPSnetbsd  OOPSrescue  OOPSsbin    OOPSusr
>> OOPSaltroot OOPScommand OOPShome    OOPSlibexec OOPSpackage OOPSroot    OOPSstand   OOPSvar
>> OOPSbin     OOPSdev     OOPSkern    OOPSmnt     OOPSproc    OOPSsandbox OOPSOOPStmp
>> 
>> vim with syntax highlighting is impossible to use in screen.
>> This a fairly fresh 2006Q2 netbsd amd64 machine being used for
>> development - terminal colors works fine outside of screen, and no
>> other problems have been observed. The .profile and .screenrc work
>> fine on similar 32 bit machines. I've tried adjusting the TERM and
>> various configs but I cannot identify the source of the problem.
>> 
>> Below is my env (from a default csh env) and .screenrc, any
>> suggestions to try?
>
>long ago, I gave up on trying to get screen to do the right thing with
>term emulation and getting the right termcap spread everywhere, etc.
>Instead, I alias screen to "screen -T vt220" and run with that.  It
>seems to handle colors just fine.


I had tried setting TERM but not using -T ...even with

 env TERM=vt220 screen -T vt220

the problem remains. The only thing I can identify as being
different with other hosts is amd64 vs i386. can other people
confirm color is working in screen on amd64?

// George 


-- 
George Georgalis, systems architect, administrator <IXOYE><