[Lowerbounds, Upperbounds]

Algorithms are everywhere.

Since STOC 2005, there has been a lot of discussion about theory funding and a task force has been set up by SIGACT to work on advocacy issues.

To start, you are referred to the post by Suresh Venkatasubramanian and a slightly later post by Lance Fortnow. Make sure you read the comment by Michael Mitzenmacher for a clarification on the purpose of the task force, directly from a task force member.

Let the message spread.

P.S. Jeff Erickson has an interesting post about basic research funding too.

You would think that there must be a utility in Unix like head or tail that would chop off the first few lines of a file and output the rest. Well, I haven’t found it yet.

In any case, perl worked.

cat foo.txt | perl -e "print splice @{[<>]}, 5″

I have installed a CAPTCHA plug-in to allow comments without requiring the poster to register and login first. Hope this will make it easier for those that don’t read this blog regularly to leave comments.

Note that if you have already logged in, you will not see any change. You only see it when posting comments anonymously.

I have come to know quite a few Pico die-hards over the years. Their primary reason for sticking with Pico is usually its simplicity. For this, I also think that Pico is hard to beat.

But it’s possible to match that simplicity while adding new features. Enter GNU Nano.

Among the many added features such as case-sensitive search, regexp search and replace, auto-indent and multiple file buffers, Nano also supports syntax highlighting. I guess even some Pico die-hards would agree that some of these are useful features. In fact I myself is a big fan of syntax highlighting (as you can see here).

Really, next time before you use Pico, give Nano a try. It may very well increase your productivity (which is why I am writing this). For starters, put these four lines into your ~/.nanorc and go:

set autoindent
set historylog
set multibuffer
set tabsize 4

Have fun!