screen-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (no subject)


From: Christian Ebert
Subject: Re: (no subject)
Date: Wed, 10 Oct 2007 13:19:43 +0200
User-agent: Mutt/1.5.16 (2007-09-19)

* ara.t.howard on Tuesday, October 09, 2007 at 11:33:41 -0600
> On Oct 9, 2007, at 11:22 AM, cga2000 wrote:
>> IIRC .. you first need to have a version of screen that supports 256
>> colors _and_ specify --enable-colors256 when you ./configure it prior
>> to compile.
> 
> right.  the Portfile on OSX does indeed specify this option to configure
> 
>> Another thing is that you are going to need to have screen point to a
>> terminfo entry that supports 256 colors.
>> 
>> I do the latter with the following .screenrc statement:
>> 
>>  term    "screen-256color-bce"
> 
> how odd, with that in my .screenrc i get the following error on startup:
> 
> "TERMCAP", line 20, col 1, terminal 'screen-256color-bce': Illegal 
> character (expected alphanumeric or @%&*!#) - ^J

AFAIR ncurses shipped with MacOS X is an old version that doesn't
have a screen-256color entry.

What gives:

$ infocmp screen-256color

If you get an error, the cleanest solution is to install a recent
ncurses version (fink's is not new enough either, don't know
about MacPorts).

c
-- 
__   _    _         _  __  _               _    
\ \ | |__| |__ _ __| |_\ \| |_ _ _ __ _ __| |_  
 \ \| '_ \ / _` / _| / /\ \  _| '_/ _` (_-< ' \ 
  \_\_.__/_\__,_\__|_\_\ \_\__|_| \__,_/__/_||_|   http://www.blacktrash.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]