One of the lists to which I subscribe has chosen to put the list as the secondary element and the individual posters as the primary. That’s fine, but the side effect of this is that when I reply to a message, it goes to the poster, and not to the list. I don’t like the behaviour, but the list admins are plainly happy with it. I resigned myself to replying-to-all for the purposes of that list, until I saw this procmail recipe:

:0:
* ^(From|To|Cc).*\@listdomain.eg
  {
    :0hf
    | /usr/bin/formail -A "Reply-To: listaddress@listdomain.eg"
    :0
    folderforlistmail
  }

I much prefer to hack the client-side then try to change policy on the server-side. I am almost universally less resistant to change than any organization.

I noticed that, within screen, I was not getting the full syntax highlighting in vim that I was expecting. Something had to be up, and it wasn’t long before I found this tip on getting full colour support for vim in screen.

After so poking about, I only used a subset of those instructions. I added this to my .screenrc:

attrcolor b ".I"
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
defbce "on"

My .vimrc got updated with this:

set t_Co=256

It did a great job, and now everything looks as it should.

I discovered an interesting new tactic in the website ad game. Like most people using Firefox, I use the AdBlock Plus extension. A short while ago, I found that Flickr stopped working very well – it was obvious to me that the CSS stylesheet wasn’t loading. After investigating, I found the reason. Some time ago, tired of Yahoo!-based banner ads, I blocked the domain yimg.com. Well, since Yahoo! bought Flickr, they have decided, ingeniously, to host the stylesheet for Flickr on yimg.com. So now, I have to unblock that domain or face an ugly Flickr. On many sites I’d be happy to deal with the ugly, but on an AJAX-intensive photo site, ugly doesn’t cut the mustard. It’s an interesting tactic, and I wonder if other companies will start to use it.