Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
A nice default screenrc
# GNU Screen - main configuration file
# All other .screenrc files will source this file to inherit settings.
# Author: Christian Wills - cwills.sys@gmail.com
# Allow bold colors - necessary for some reason
attrcolor b ".I"
# Tell screen how to set colors. AB = background, AF=foreground
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
# Enables use of shift-PgUp and shift-PgDn
termcapinfo xterm|xterms|xs|rxvt ti@:te@
# Erase background with current bg color
defbce "on"
# Enable 256 color term
term xterm-256color
# Cache 30000 lines for scroll back
defscrollback 30000
# New mail notification
backtick 101 30 15 $HOME/bin/mailstatus.sh
hardstatus alwayslastline
# Very nice tabbed colored hardstatus line
hardstatus string '%{= Kd} %{= Kd}%-w%{= Kr}[%{= KW}%n %t%{= Kr}]%{= Kd}%+w %-= %{KG} %H%{KW}|%{KY}%101`%{KW}|%D %M %d %Y%{= Kc} %C%A%{-}'
# change command character from ctrl-a to ctrl-b (emacs users may want this)
#escape ^Bb
# Hide hardstatus: ctrl-a f
bind f eval "hardstatus ignore"
# Show hardstatus: ctrl-a F
bind F eval "hardstatus alwayslastline"

jenia commented Jan 31, 2015

Thanks very much for the config file.
I have a small problem with it though. I often get this error message on the bottom line: Message 12549 of 12588 bytes to small.

Actually, its the
hardstatus string '%{= Kd} %{= Kd}%-w%{= Kr}[%{= KW}%n %t%{= Kr}]%{= Kd}%+w %-= %{KG} %H%{KW}|%{KY}%101`%{KW}|%D %M %d %Y%{= Kc} %C%A%{-}'

line that causes it. What is that? How can I remove it?

rdpanek commented Aug 10, 2015

Thanks

qayshp commented Oct 15, 2015

What does your mailstatus.sh script print? Just an unread message count?

Amazing config file. I had fixed the annoying screen 8 colors using your config file.Thanks

Thanks a lot!

micwin commented Jul 19, 2016

wow, thanks a lot!

Good work,.. thanks a lot !!

Great screen configuration, thank you for sharing

Excellent example, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment