I still haven’t struck the balance I’d like between posting links and posting longer features here. I had the link blog for awhile, but nobody read it, so I gave up on it with the intent of posting the links to the main blog, but my output has diminished significantly. I still track lots of links, by way of my del.icio.us account. I don’t want to just repost that list of links here because some of those links aren’t really very interesting.
So now my new idea is to post a wrapup of what I’m finding here every day or two in a more narrative form. This is the first attempt.
My interest in all things iPhone continues. Yesterday I saw a big list of iPhone bugs, a big list of Web apps designed for iPhone, and a method for using your own ringtones.
I’m also interested in GNU Screen. I haven’t really started using it, but I am collecting information about it. Yesterday I saw a blog post about how to set up the status line in Screen and found a Screen tutorial. Two different people have told me how useful they find Screen lately, so I feel like I’m missing out.
Finally, I grabbed links to three different responses to Jakob Nielsen’s anti-blog article that is getting so much attention. Scott Rosenberg dissents. Jeff Atwood concurs. Christopher Fahey eviscerates.
July 17, 2007 at 3:07 pm
I had the link blog for awhile, but nobody read it
I did! I miss it.
July 17, 2007 at 4:18 pm
screen is awesome. One of the things about being a regular IRC addict^Wuser is that you learn about screen at a relatively early age.
July 17, 2007 at 4:59 pm
I also liked and miss the link blog; I read it via the feed you had for it.
GNU screen is an indispensable part of my computing toolkit — I have one session running at home, one running at work, and I just reconnect as needed. Utterly wonderful.
July 17, 2007 at 5:57 pm
you dont need screen if you use emacs
July 18, 2007 at 12:56 am
&uotThe best part about screen is that you can script it – I routinely use this for software deployment to run a command on a hundred systems which may prompt in some cases which require human intervention. It’s basically a for loop which does this to run a command in a new screen window with the title set to the hostname of the remote machine:
system(“screen -X screen -t ‘$Hostname’ sh -c ‘$cmd || read -p \”SSH returned an error on $Hostname\”‘;);
One other use of screen which is less obvious: we have a few programs which send lots of status output. If you need to run one of these remotely that can actually cause a bit of overhead; running it under a detached screen session avoids that problem since it can run at full speed without the remote terminal overhead.
This is a handy thing for your .bash_profile – it reports any detached screen sessions when you login to a system:
if [ -x “
which screen” ]; thenThis will report any de screen sessions:
SCREENS=
screen -list | grep -F '(Detached)' | sed -e 's/^[[:space:]]*/\t/'if [ ! -z “$SCREENS” ]; then echo “Detached screen sessions:” echo “$SCREENS” fi fiJuly 18, 2007 at 7:45 pm
Love your blog the way its been. I read the links blog. I’m sure I will like the new style too.
July 19, 2007 at 11:54 am
Mark Pilgrim has some interesting ways of hacking screen. Might want to check it out:
http://diveintomark.org/archives/2007/03/15/good-easy-2007