Like usual, there are almost certainly specific GNOME or KDE tools to accomplish this goal. Since I’m not running those, however, I’ll stick to tools available in almost any X.Org environment (I happen to be using Ratpoison).

First, some terminology. A scancode is the lowest level of identification for a key. If your key doesn’t have a scancode, you’re out of luck – the kernel doesn’t recognize the key at all. A keycode is the next level of identification. If your key’s scancode is identified with a keycode, then there’s just one more step to make it do what you want. The last level of identification is a symbol. A scancode is mapped to a keycode, which is mapped to a symbol (for example, the letter “e” or “Caps Lock”).

Keycodes

Starting out, none of my hotkeys were mapped to symbols, some were mapped to keycodes, and some only had scancodes (thankfully there were no completely “dead” keys). You can check if a key has a keycode by using xbindkeys. In a terminal (in X – not a console) type
[plain]xbindkeys -k[/plain]
followed by the key you want to check. Here’s an example of the output from my “Back” hotkey (before I bound it using xbindkeys, but after I assigned a keycode to the scancode, as described at the end of this post):
[plain]
james@tv:~$ xbindkeys -k
Press combination of keys or/and click under the window.
You can use one of the two lines after “NoCommand”
in $HOME/.xbindkeysrc to bind a key.
“(Scheme function)”
m:0×10 + c:211
Mod2 + NoSymbol
[/plain]

Binding keycodes to actions

Using the output from xbindkeys -k, it’s easy to bind a key to an action. This will be configured in the ~/.xbindkeysrc file (you may need to create it). It will take effect when you run xbindkeys. You’ll probably want to call it in your ~/.xinitrc file. Here’s an example of the format from my .xbindkeysrc:
[plain]
# internet key
“firefox”
m:0×10 + c:178

# play/pause key
“mpc toggle”
m:0×10 + c:162

# stop key
“mpc stop”
m:0×10 + c:164

# previous track key
“mpc prev”
m:0×10 + c:144

# next track key
“mpc next”
m:0×10 + c:153

# volume up key
“amixer set ‘Headphone’ 1%+ ; amixer set ‘PCM’ 1%+”
m:0×10 + c:176

# volume down key
“amixer set ‘Headphone’ 1%- ; amixer set ‘PCM’ 1%-”
m:0×10 + c:174

# mute key
“amixer set ‘Headphone’ toggle ; amixer set ‘PCM’ toggle”
m:0×10 + c:160
[/plain]
It’s a pretty simple format. Obviously the “#” precedes a comment (and is optional, but recommended). The next line is the command you want the hotkey to run (surrounded by quotes). You’ll recognize the final line from the output of xbindkeys -k. I’m not sure if you can use either output line (or both) but mine works fine with just the first line following the "(Scheme function)" line.

That’s all there is to it… unless your key does not have a keycode.

Mapping scancodes to keycodes

If xbindkeys -k does not recognize your key, it’s probably not associated with a keycode. You can check if the key has a scancode (in other words, if the kernel recognizes the key) by pressing the key and then checking dmesg to see if the key was mentioned. Here’s an example of what it will look like (from pushing my “Back” hotkey, before I assigned it to a keycode):
[plain]
james@tv:~$ dmesg | tail -4
[ 48.274918] atkbd.c: Unknown key pressed (translated set 2, code 0×83 on isa0060/serio0).
[ 48.274918] atkbd.c: Use ‘setkeycodes e003 ‘ to make it known.
[ 48.789832] atkbd.c: Unknown key released (translated set 2, code 0×83 on isa0060/serio0).
[ 48.789832] atkbd.c: Use ‘setkeycodes e003 ‘ to make it known.
[/plain]
If you get similar output, you’re key has a scancode (and is not mapped to a keycode). You can use setkeycodes to assign a keycode to the key. Before doing this, however, you’re going to want to make sure that you don’t assign it to a keycode that’s already in use. You can find this out by looking at your keymap.
[bash]
james@tv:~$ cp /etc/console/boottime.kmap.gz .
james@tv:~$ gunzip boottime.kmap.gz
james@tv:~$ less boottime.kmap
[/bash]
[plain]
– SNIP –

keycode 81 = KP_3
altgr keycode 81 = Hex_3
alt keycode 81 = Ascii_3
keycode 82 = KP_0
altgr keycode 82 = Hex_0
alt keycode 82 = Ascii_0
keycode 83 = KP_Period
altgr control keycode 83 = Boot
control alt keycode 83 = Boot
keycode 84 = Last_Console
keycode 85 =
keycode 86 = less greater bar
alt keycode 86 = Meta_less
shift alt keycode 86 = Meta_greater
keycode 87 = F11 F23 Console_23 F35
alt keycode 87 = Console_11
control alt keycode 87 = Console_11
keycode 88 = F12 F24 Console_24 F36
alt keycode 88 = Console_12
control alt keycode 88 = Console_12
keycode 89 =
keycode 90 =
keycode 91 =
keycode 92 =
keycode 93 =
keycode 94 =
keycode 95 =
keycode 96 = KP_Enter
altgr keycode 96 = Hex_F
keycode 97 = Control
keycode 98 = KP_Divide
altgr keycode 98 = Hex_B
keycode 99 = Control_backslash
alt keycode 99 = Meta_Control_backslash
shift alt keycode 99 = Meta_Control_backslash
control alt keycode 99 = Meta_Control_backslash
keycode 100 = AltGr
keycode 101 = Break
keycode 102 = Find

– SNIP –
[/plain]
You can see that some keycodes are not being used (89-95, for example), so those are safe to use. (By the way, I’ve heard that you’re supposed to pick a keycode between 1-127, but I don’t know why, or what happens if you don’t – I’ve never used one outside of that range).

You can then assign a scancode to one of these unused keycodes using setkeycodes (as root).
[plain]setkeycodes 0×83 89[/plain]
The above code assigns the scancode from my “Back” hotkey to the unused keycode “89″. Once that’s been done, you can use xbindkeys -k (as described above) to get the correct identifier to bind the key using xbindkeys.

Assuming you want to use this binding after you reboot, you’ll want to add the setkeycodes command to /etc/rc.local. Here’s an example of mine:
[bash]
james@tv:~$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will “exit 0″ on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

## James added to map the “back”, “shopping cart”, and “?” keys on Gateway keyboard
setkeycodes 0×83 89 &
setkeycodes 0×81 90 &
setkeycodes 0×82 91 &

exit 0
[/bash]

Please feel free to mention better or alternate ways, or anything that I’ve got wrong.

The games are:

• World of Goo
• Aquaria
• Gish
• Lugaru
• Penumbra: overture

You can buy the bundle here: http://www.wolfire.com/humble

First, get the package

Go to http://www.google.com/chrome/eula.html and select the 32-bit .deb for Debian/Ubuntu, then click “Accept and Install”. This will download google-chrome-beta_current_i386.deb.

Optional: Prevent Chrome from adding the Google repository

If you want Chrome to keep itself up-to-date, don’t do this step. However, if you just want to check Chrome out without changing too much, you might want to type the following command at the command line:
[bash light="true" highlight="1"]sudo touch /etc/default/google-chrome[/bash]

Install with DPKG

In the directory where you downloaded Chrome:
[bash light="true" highlight="1"]sudo dpkg –install google-chrome-beta_current_i386.deb[/bash]
In my case, I didn’t have the necessary dependencies, so I got the following errors:
[bash light="true"]
james@tv:~$ sudo dpkg –install google-chrome-beta_current_i386.deb
Selecting previously deselected package google-chrome-beta.
(Reading database … 24475 files and directories currently installed.)
Unpacking google-chrome-beta (from google-chrome-beta_current_i386.deb) …
dpkg: dependency problems prevent configuration of google-chrome-beta:
google-chrome-beta depends on libgconf2-4; however:
Package libgconf2-4 is not installed.
google-chrome-beta depends on libxslt1.1; however:
Package libxslt1.1 is not installed.
google-chrome-beta depends on libxss1; however:
Package libxss1 is not installed.
google-chrome-beta depends on xdg-utils (>= 1.0.1); however:
Package xdg-utils is not installed.
dpkg: error processing google-chrome-beta (–install):
dependency problems – leaving unconfigured
Processing triggers for menu …
Processing triggers for man-db …
Errors were encountered while processing:
google-chrome-beta
[/bash]
You can fix that with apt-get, like so:
[bash light="true" highlight="1"]sudo apt-get -f install[/bash]
This will grab all of the dependencies Chrome needs. Here’s the output (you’ll need to type “y” when prompted):

[bash collapse="true" gutter="false" toolbar="false"]
james@tv:~$ sudo apt-get -f install
Reading package lists… Done
Building dependency tree
Reading state information… Done
Correcting dependencies… Done
The following extra packages will be installed:
gconf2-common libgconf2-4 libidl0 liborbit2 libxslt1.1 libxss1 shared-mime-info xdg-utils
Suggested packages:
desktop-file-utils libgnome2-0 exo-utils libgnomevfs2-bin kdelibs4c2a konqueror
The following NEW packages will be installed:
gconf2-common libgconf2-4 libidl0 liborbit2 libxslt1.1 libxss1 shared-mime-info xdg-utils
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 3047kB of archives.
After this operation, 11.1MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://ftp.us.debian.org lenny/main gconf2-common 2.22.0-1 [1532kB]
Get:2 http://ftp.us.debian.org lenny/main libidl0 0.8.10-0.1 [87.6kB]
Get:3 http://ftp.us.debian.org lenny/main liborbit2 1:2.14.13-0.1 [249kB]
Get:4 http://ftp.us.debian.org lenny/main libgconf2-4 2.22.0-1 [242kB]
Get:5 http://ftp.us.debian.org lenny/main libxslt1.1 1.1.24-2 [227kB]
Get:6 http://ftp.us.debian.org lenny/main libxss1 1:1.1.3-1 [11.9kB]
Get:7 http://ftp.us.debian.org lenny/main xdg-utils 1.0.2-6.1 [54.3kB]
Get:8 http://ftp.us.debian.org lenny/main shared-mime-info 0.30-2 [644kB]
Fetched 3047kB in 7s (433kB/s)
Selecting previously deselected package gconf2-common.
(Reading database … 24798 files and directories currently installed.)
Unpacking gconf2-common (from …/gconf2-common_2.22.0-1_all.deb) …
Selecting previously deselected package libidl0.
Unpacking libidl0 (from …/libidl0_0.8.10-0.1_i386.deb) …
Selecting previously deselected package liborbit2.
Unpacking liborbit2 (from …/liborbit2_1%3a2.14.13-0.1_i386.deb) …
Selecting previously deselected package libgconf2-4.
Unpacking libgconf2-4 (from …/libgconf2-4_2.22.0-1_i386.deb) …
Selecting previously deselected package libxslt1.1.
Unpacking libxslt1.1 (from …/libxslt1.1_1.1.24-2_i386.deb) …
Selecting previously deselected package libxss1.
Unpacking libxss1 (from …/libxss1_1%3a1.1.3-1_i386.deb) …
Selecting previously deselected package xdg-utils.
Unpacking xdg-utils (from …/xdg-utils_1.0.2-6.1_all.deb) …
Selecting previously deselected package shared-mime-info.
Unpacking shared-mime-info (from …/shared-mime-info_0.30-2_i386.deb) …
Processing triggers for man-db …
Setting up gconf2-common (2.22.0-1) …

Creating config file /etc/gconf/2/path with new version
Setting up libidl0 (0.8.10-0.1) …
Setting up liborbit2 (1:2.14.13-0.1) …
Setting up libgconf2-4 (2.22.0-1) …
Setting up libxslt1.1 (1.1.24-2) …
Setting up libxss1 (1:1.1.3-1) …
Setting up xdg-utils (1.0.2-6.1) …
Setting up google-chrome-beta (5.0.375.29-r46008) …
Setting up shared-mime-info (0.30-2) …
Processing triggers for menu …
[/bash]
Now, I’m not sure if this last step is actually necessary, but I figured it couldn’t hurt to repeat the original dpkg command, just to make sure it works with no errors (again, in the directory where you downloaded the .deb):
[bash light="true" highlight="1"]sudo dpkg –install google-chrome-beta_current_i386.deb[/bash]
This time it worked fine:
[bash light="true"]
james@tv:~$ sudo dpkg –install google-chrome-beta_current_i386.deb
(Reading database … 25041 files and directories currently installed.)
Preparing to replace google-chrome-beta 5.0.375.29-r46008 (using google-chrome-beta_current_i386.deb) …
Unpacking replacement google-chrome-beta …
Setting up google-chrome-beta (5.0.375.29-r46008) …
Processing triggers for menu …
Processing triggers for man-db …
[/bash]

Launch Chrome

[bash light="true" highlight="1"]google-chrome[/bash]

This title of this post is not entirely accurate. The post is actually about a script that will list files and directories in the same format as ls -l (the “long listing” format of the ls command), except it will correctly report the size of directories (and all of the files within them). Technically, it is actually in the format of ls -lhL.

This is functionally very different than the output of ls. Typically ls lists the size of directories not including their contents. This produces a very small number, which is the amount of disk space the directory’s meta-data takes up (i.e. the names of files within the directory). Here is an example:
[bash light="true"]ls -lhL[/bash]
[plain]
total 116K
drwxr-x— 1 james users 44K 2010-04-22 17:21 movies
drwxr-x— 1 james users 48K 2010-04-03 22:22 music
drwxr-x— 1 james users 0 2009-12-11 16:20 photos
drwxr-x— 1 james users 4.0K 2009-12-13 22:36 data
drwxr-x— 1 james users 20K 2010-04-27 00:56 tv
[/plain]
And here is an example of the output of the script (note the size of the directories):
[plain]
drwxr-x— 1 james users 178G 2010-04-22 17:21 movies
drwxr-x— 1 james users 26G 2010-04-03 22:22 music
drwxr-x— 1 james users 9.9G 2009-12-11 16:20 photos
drwxr-x— 1 james users 27G 2009-12-13 22:36 data
drwxr-x— 1 james users 135G 2010-04-27 00:56 tv
[/plain]
That’s a pretty big difference. Note that if all you’re interested in is the permissions, modification time, and filename, using ls -lh is a much better choice – it’s extremely fast and gives you all the information you need. However, if you want to know how much space the contents of each directory is using, you should use the following script:
[bash gutter="1"]
#!/bin/bash
# script to display the sizes of files and directories in the format of ls -lhL
## note that large space on line 9 (the ‘ ‘ that follows “cut -d”) is a tab, created in a terminal with CTRL+v then TAB
for x in *;
do
y=”$(echo “$x” | sed -e ‘s/\[/\\[/g' -e 's/]/\\]/g’)”
echo -e \
“$(ls -lL | grep “[0-9]\{2\}:[0-9]\{2\} $y$” | sed ‘s/[ ][ ]*/ /g’ | cut -d ‘ ‘ -f 1-4) \
$(du -sh “$x” | cut -d ‘ ‘ -f 1)” \
“$(ls -lL | grep “[0-9]\{2\}:[0-9]\{2\} $y$” | sed ‘s/[ ][ ]*/ /g’ | cut -d ‘ ‘ -f 6-20 )”;
done \
| column -t \
| sed -e ‘s/[ ]\([ ][ ]*\)/\1/g’ \
| sed -e ‘s/[ ][ ]*/ /8g’ \
| sed ‘s/\([ ][ ]*\)\([^ ]*\)\([ ]\)\([ ]*\)\([^ ]*[ ]*[^ ]*[ ]*\)\([^ ]*\)\([ ]\)\([ ]*\)/\1\4\2\3\5\8\6\7/’
[/bash]
NOTE – The script is not displayed entirely correctly in this post; on line 8, the multiple spaces in single-quotes (following cut -d) should be a TAB. Although it’s displayed incorrectly on the page, if you use either the “view source” or “copy to clipboard” buttons (top-right of the script when you hover over it), it will use the correct character. You can also produce this character in a terminal with CTRL+v followed by TAB.

This script should be named something convenient and saved somewhere in your $PATH. I call the script lsd and save it in “/home/james/bin”.

How the script works

If you’re the kind of person who likes to know what a script does before copying it from the internet and running it, here’s what’s going on in this script. Paragraphs are labeled by the script’s line numbers.

Lines 4-11. This is a for loop that is run on every (non-hidden) file in your current directory (*). $x is the variable that holds one of the directory’s filenames per iteration.

Line 6. $y is a variable that equals $x, except brackets (“[" and "]“) are replaced by escaped brackets (“\[" and "\]“), in order to avoid conflict with grep’s regular expressions matching.

Lines 7-10. These lines are all part of a long echo command which arranges the data in the same format as ls -lhL. It is echoing three separate command substitution variables, separated by spaces.

Line 8. The first of three command substitutions. Gets a long directory listing, greps out the single line that matches $x, removes extra spaces between sections, and then chops off the 2nd part of the line at the point where the directory size will be displayed.

Line 9. The second of three command substitutions. Gets the size of $x using du -sh and then chops off the end of the line, leaving only the size.

Line 10. The third of three command substitutions. Gets a long directory listing, greps out the single line that matches $x, removes extra spaces between sections, and then chops off the 1st part of the line up to the point after where the directory size will be displayed. Script lines 8, 9, and 10 will form a single line of output for each iteration of the for loop.

Lines 12-15. Each of these lines formats the script’s output to match the style of ls -lhL.

Line 12. Sorts the output into columns using column -t.

Line 13. Removes extra spaces according to the following rule: for every group of 2 or more consecutive spaces, subtract one space from that group.

Line 14. Removes extra spaces from the last part of the lines, ensuring that filenames containing spaces do not have multiple consecutive spaces.

Line 15. Swaps certain groups of spaces around in order to match the justification style of ls -lhL. Specifically, user and group names are justified left, while file sizes are justified right.

Please leave a comment if you’ve tried this script and found any bugs in it.

I like the Super Contacts app for the Palm Pre, and I decided to put it in the quicklaunch dock instead of Palm’s default Contacts app. The only problem with this is that the Super Contacts app is really ugly (my apologies, guys-who-made-it, I admit I’m shallow). Here’s what I did to replace it with Palm’s Contacts icon.

You’ll need to have command line access to your Pre. This can be done with the terminal app, but using it for more than a few seconds will probably make you want to kill yourself. I suggest using SSH.

First, back everything up:
[bash]
cd /media/cryptofs/apps/usr/palm/applications/com.orgorganization.app.supercontacts
cp icon.png icon.png.backup
cp icon32x32.png icon32x32.backup
cp miniicon.png miniicon.png.backup
[/bash]
Sadly, I don’t even know which of those files (icon.png, icon32x32.png, or miniicon.png) is used for the dock icon, because my changes weren’t updated until I rebooted.

Replace the Super Contacts icon with the Palm Contacts icon:
[bash]
cp /usr/palm/applications/com.palm.app.contacts/icon.png /media/cryptofs/apps/usr/palm/applications/com.orgorganization.app.supercontacts/icon.png
cp /usr/palm/applications/com.palm.app.contacts/icon.png /media/cryptofs/apps/usr/palm/applications/com.orgorganization.app.supercontacts/icon32x32.png
cp /usr/palm/applications/com.palm.app.contacts/icon.png /media/cryptofs/apps/usr/palm/applications/com.orgorganization.app.supercontacts/miniicon.png
[/bash]
That should cover all of your bases. Just reboot and the old Super Contacts icon in the dock should have been replaced by the Palm Contacts icon.

1. Go to Google’s Experiment Search page (part of Google Labs) here: http://www.google.com/experimental/
2. Press the “Join this experiment” button at the top, right-hand corner of the “Keyboard shortcuts” experiment section
3. Enjoy not seeing Google’s new layout any more on search results
4. Bonus Points – Enjoy the Keyboard Shortcuts experiment, which is really fantastic. It lets you navigate Google search results with keyboard shortcuts that will feel very natural to fans of Linux terminal apps. (Notably, “j” navigates down, “k” navigates up.) These are also the shortcuts used in Gmail, Google Reader, and the Boston Globe’s “Big Picture” (which is fantastic).

Please leave a comment if this doesn’t work for you, or you know a better way to do it, or if you think the new layout has some redeeming quality that I’m missing.

Step 1
/etc/inittab & mingetty

mingetty is an alternative to getty, which (for the sake of simplicity) I describe as the linux login program. You’ll need to install mingetty:

[bash]
#as root (i.e., using either su or sudo)
apt-get install mingetty
[/bash]

Isn’t Debian easy? We’re going to use mingetty to auto-login on tty6 (which you can access with ctrl+alt+F6). You’ll need to edit /etc/inittab:

[bash]
#First (always), make a backup copy
cp /etc/inittab ~/inittab.backup
[/bash]

[bash]
#note that I’m using “vim” here – that’s my editor of choice, but you can use whatever text editor you please (nano is easy)
#as root
vim /etc/inittab
[/bash]

Find this section:

[bash]
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
[/bash]

and change it to this:

[bash]
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
#6:23:respawn:/sbin/getty 38400 tty6
6:23:respawn:/sbin/mingetty –autologin james –noclear tty6
[/bash]

(By the way, I should note that I usually duplicate lines I’m going to change, and then comment-out one and make my changes to the other one, so I’ll know what the line used to be. Feel free to delete the commented-out lines if you like.) Obviously you’ll also want to replace “james” with your username (unless by chance your username is also “james”).

That’s the end of step one. At this point, your computer should boot just like normal, but if you go to tty6 (again, ctrl+alt+F6), you’ll find that you’re already logged in on that tty.

Step 2
~/.profile

The ~/.profile is a script that is run after opening a login shell. There’s probably some stuff already in there that can be left alone. You’ll need to add the following IF statement, which will automatically run startx (which, appropriately, starts X) when someone logs in to tty6 (which will happen automatically, thanks to Step 1).

[bash]
#First (always), make a backup copy
cp ~/.profile ~/.profile.backup
[/bash]

[bash]
# if logging into tty6 (which will autologin), run startx
if [ -z "$DISPLAY" ] && [ $(tty) = /dev/tty6 ] ; then
startx ;
fi
[/bash]

That’s the end of Step 2. Now your computer will auto-login on tty6 (thanks to /etc/inittab), and then automatically start X (thanks to ~/.profile). Now all that’s left is to start ratpoison.

Step 3
~/.xinitrc

The .xinitrc is a script that consists of commands you want to run when you start X. I have around 11 commands in my .xinitrc, but there’s only one that’s necessary to start ratpoison (which is the window manager I use — you may want to use a different WM, and if so, alter your .xinitrc accordingly). This needs to be the last command listed in your .xinitrc:

[bash]
ratpoison
[/bash]

That last step seems fairly obvious, but maybe not if this is your first time. Feel free to leave a comment if you have any questions or suggestions.

Reasons:

• Bluehost seems way less gimmicky
  • There aren’t ads plastered everywhere in Bluehost
  • They aren’t trying to constantly upsell (in fact, there’s really not much to move up to – they just seem to have the one plan)
  • They don’t charge extra for private domain registration
• The Bluehost interface is clean and uncluttered
• Setting up WordPress is pretty easy with either site, but it seems easier with Bluehost
• Bluehost’s cPanel is easier to use

I’ve never had major problems with either site, so I can’t compare the quality of their customer service. The customer support at both sites have impressed me the few times I’ve interacted with them (Godaddy’s telephone support is really nice).

This isn’t intended to bash Godaddy – they didn’t treat me poorly, and I would have never tried Bluehost had I not heard such positive recommendations. However, after trying them both, I’ll be sticking with Bluehost.

[bash]
#!/bin/bash
## Shortcut to search, add, and play an album (after clearing current playlist).
## Use -a (for “add”) to add the album to the playlist without clearing current playlist.

if [ $1 = -a ]
then
shift
mpc search album “$*” | mpc add ; mpc play
exit
fi

mpc clear
mpc search album “$*” | mpc add ; mpc play
[/bash]

The usage is simple:
[bash]album abbey[/bash]
The above command would stop the song currently playing, clear the current playlist and replace it with The Beatles’ Abbey Road, and start playing it. If I had another album with “abbey” in the name, it would have loaded that one as well. Spaces are included as part of the search string — for example, this also works:
[bash]album abbey road[/bash]

You can use the “-a” switch to add the album to the current playlist. It won’t interrupt what’s currently playing, it will only put the new album in the queue.
[bash]album -a abbey road[/bash]

It’s not hard to fix, but the commands changed at one point, and I was still using the old commands. This is what I had in my .ratpoisonrc (which wasn’t working):
[bash]
defborder 0
defpadding 0 0 0 0
defbarpadding 0 0
[/bash]
That should be replaced by this:
[bash]
set border 0
set padding 0 0 0 0
set barpadding 0 0
[/bash]