I have beaten gnu screen into submission. For ages it has refused
to let me start with screen number 1 instead of 0. Binding c to
screen 1 was supposed to fix this. The cause? My fingers were too
fast. Turns out that I need to also bind Ctrl+c. For your
convenience, copy and paste the below into your ~/.screenrc if you
have a similar problem.
bind c screen 1 bind ^c screen 1 bind 0 select 10
Published on November 24, 2008 Comments
· · ·
Recently I found myself getting tired of Pidgin‘s multi-window interface and began searching for alternatives. Because I’m already on IRC all the time anyway, I decided to take a shot at Bitlbee. Bitlbee takes all the useful features of Pidgin and sticks them in a familiar IRC-ish interface. The only annoying part was that the message notification Pidgin gave me was gone — no more color changing tags/taskbar. Enter urgency hints.
I’d played with them before when hacking on dwm. In fact, I added this feature to my dwm because of Pidgin in the first place. My challenge now was to get irssi to pass the hint to gnu-screen, to pass the hint to urxvt over an ssh session, to pass it to my window manager. This was suprisingly easy. Three configs are involved: ~/.irssi/config, ~/.screenrc, and ~/.Xdefaults. Additions are shown below.
~/.irssi/config
settings = { "fe-common/core" = { beep_msg_level = "NOTICE MSGS HILIGHT"; bell_beeps = "no"; }; };
~/.screenrc
vbell off bell_msg '^G'
~/.Xdefaults
urxvt*urgentOnBell: true
With these three settings, I now get a nice notification when receiving a message in Bitlbee or irssi. This has a nice side effect too. Many cli apps can send a bell when they need your attention. Mutt, for instance, can now notify you about new mail.
Published on November 17, 2008 Comments