I’ll just write about two things that I’ve worked out recently.

Lesson #1: Read the README file.

Well duh, you say. The story is, I’ve had the bash_completion script for some time (a really useful extension that makes typing on the command line that much easier), but I’ve never quite worked out why it didn’t work. Now I know why. It’s because I naively assumed that the bash_completion.sh script was the meat of it, and simply called it from .bashrc, expecting it to just work. It would, ordinarily, but I don’t have it installed in /etc which is where it expects to be (it’s in my home directory). If you have somewhere else like me, you will need to set the $BASH_COMPLETION variable and modify the bash_completion.sh script to reflect where you’ve actually put it.

Lesson #2: If you didn’t set up the system yourself, things might not be as you expect them to be.

SUITS has a bunch of useful scripts that you can use to improve your command line experience on the undergraduate IT servers, and I copied them over to my account on nointrigue.com because I like them so much. One of these scripts sets nice colours for the command line. It was all working fine until I realised TortoiseSVN could no longer access the Subversion repositories via svn+ssh, failing with the error “connection closed unexpectedly”. I figured something I added recently was injecting garbage into the stream. It turns out it was the colour-adding script! But why? It was protected like this:

if [ -n "$PS1" ]; then
        . ~/.bash/colors
fi

That means that it should only have been run if it was running in an “interactive” terminal, and the colour-adding script should not have been called if I was using svn+ssh. After some more poking around, I found this in /etc/bashrc (which was being called from .bashrc):

# For some unknown reason bash refuses to inherit
# PS1 in some circumstances that I can't figure out.
# Putting PS1 here ensures that it gets loaded every time.

Uhh, ok, nice work, Bluehost. I guess not many of their customers actually use ssh. At least there was a comment.

But even if it was called, why the colour-adding script was failing in the first place? It turns out that tput colors fails if $TERM is not set, which happens to be so when using svn+ssh. (Actually, this would not normally prevent me from accessing my Subversion repositories. The command line svn seems to ignore errors; however, TortoiseSVN dies the moment it sees anything untoward.) My ultimate solution was to simply pipe error to /dev/null.

An error has occurred while interacting with the database.

If you get this error, don’t panic. For me, it turned out that one of the database tables was corrupted and needed repairing. Log in to phpMyAdmin or to the mysql console and check whether any of the tables are listed as corrupt. In my case, it turned out to be g2_CacheMap.

I snooped around some forums, and in the threads that had responses (a lot of forums have questions left unanswered unfortunately), it seems like the blame lies with your host having a bad mysql setup or bad hard drives that corrupt at random. Shame on you, Bluehost.

It’s reticent of me not to have posted regularly recently, as I promised to do earlier on. However, blogging is something that requires momentum - for me at least, once I start writing, I can’t stop, but it’s getting started that’s the problem. Maybe that’s why my law assignments always get written so late. I lost momentum in the lead-up to honours thesis submission and then the inability of the older version of Opera to cooperate with WordPress while I was in Hong Kong was a bit of a showstopper. But maybe I’m just making up excuses.

Writing regularly is a good thing to do: I think, like muscles, writing ability gets lost if you don’t use it. Joel Spolsky, a prominent software developer and writer who anyone interested in the business of software should read, mentioned in his blog that one of the best courses he ever took at university was one that involved copious amounts of writing: “Being able to write clearly on technical topics is the difference between being a grunt individual contributor programmer and being a leader”.

I’ll try and regain some momentum in the immediate future, and I hope that I’ll regain your trust as readers.*

* The less I write, the less people read my blog (as measured by the statistics I get). Makes sense doesn’t it?

Speaking of RSS feeds, if you haven’t subscribed to my blog via RSS, it’s easy - just click the Entries RSS link on the left sidebar.

Also, I’ve decided to license to license my blog under a Creative Commons license. Sharing is caring.

Onwards!

For the last couple of weeks, I’ve been bludging my time away suffering under post-exam traumatic stress syndrome (PETSS), which is the one of the most terrible diseases known to mankind, or at least to university students. I’d like to think it was justified, and here is a quick summary of the past semester to prove my point:

Argh.

In actual fact, I’ve been putting off writing because I’ve been wanting to reform the categories and the things that I write about (the three categories aren’t working very well), among other changes I want to do to my site. but I couldn’t be bothered doing that until I bothered logging on to my blog. And I couldn’t be bothered logging on because I knew I’d have to go and do the difficult task of reorganising things. This is known as a deadlock. Thankfully, I’m not your average office Turing machine.