Re: can 256color be recognized automatically?

2009-03-14 Thread Tom Scogland
Hence the above posting of the variable source. =) source ${HOME}/.screenrc-${TERM} Works perfectly, great for makefiles too where you want to split things up based on an environment variable. Also, "read backlog" might be a good addition to the "awake (or sober)" list. =P On Sat, Mar 14, 2009

Re: can 256color be recognized automatically?

2009-03-14 Thread Chris Jones
On Sat, Mar 14, 2009 at 09:08:54AM EDT, Christian Ebert wrote: > * Chris Jones on Saturday, March 14, 2009 at 05:21:46 -0400 > > On second thoughts .. the above doesn't make sense.. > > > > :-( > > ;-) Yeah .. wait till you're fully awake (or sober) till you post. > > If I don't hear any more I

Re: screen command creates new window instead of new instance.

2009-03-14 Thread Chris Jones
On Sat, Jan 31, 2009 at 07:42:38AM EST, Geraint Edwards wrote: > The workaround is simple - remove (unset) STY within the xterm shell. Or start your second session like so: $ screen -m -c .other_screenrc The "-m" likely does the same thing as unsetting STY but I found this while reviewing scree

Re: can 256color be recognized automatically?

2009-03-14 Thread Christian Ebert
* Tom Scogland on Saturday, March 14, 2009 at 10:03:07 -0400 > my solution to this problem was to have a line in my screenrc like the > following > source ${HOME}/.screenrc-${TERM} > > and just create a few files like .screenrc-xterm and > .screenrc-xterm-256color etc that have all my terminal spe

Re: can 256color be recognized automatically?

2009-03-14 Thread Tom Scogland
my solution to this problem was to have a line in my screenrc like the following source ${HOME}/.screenrc-${TERM} and just create a few files like .screenrc-xterm and .screenrc-xterm-256color etc that have all my terminal specific settings in them, including 256 color support. just my $0.02 On S

Re: can 256color be recognized automatically?

2009-03-14 Thread Christian Ebert
* Chris Jones on Saturday, March 14, 2009 at 05:21:46 -0400 > On second thoughts .. the above doesn't make sense.. > > :-( ;-) If I don't hear any more I might go for something like: if echo $TERM | grep -E -e "-[0-9]+color$" > /dev/null 2>&1 then screen -T "screen-${TERM##*-}" else sc

Re: can 256color be recognized automatically?

2009-03-14 Thread Christian Ebert
* Chris Jones on Saturday, March 14, 2009 at 04:50:09 -0400 > On Thu, Mar 12, 2009 at 06:57:38PM EDT, Christian Ebert wrote: >> At the moment I have to set explicitly >> >> term "screen-256color" > >> to get 256 colors working. Otherwise $TERM stays simply "screen", >> even when called from an xt

Re: can 256color be recognized automatically?

2009-03-14 Thread Chris Jones
On Sat, Mar 14, 2009 at 04:50:09AM EDT, Chris Jones wrote: > ncl=$(tput colors) > > case "$ncl" in > '16') > TERM=screen /usr/local/bin/screen > ;; > '256') > TERM=screen-256color /usr/local/bin/screen > ;; > esac On second thoughts .. the above doesn't make sense.. :-( If

Re: can 256color be recognized automatically?

2009-03-14 Thread Chris Jones
On Thu, Mar 12, 2009 at 06:57:38PM EDT, Christian Ebert wrote: > Hi, > > $ screen -v > Screen version 4.01.00devel (FAUd87a0d8) 2-May-06 > > that's latest from git repo, and latest ncurses(w) + xterm. > > At the moment I have to set explicitly > > term "screen-256color" > to get 256 colors wor