I love the keyboard shortcuts in Gmail, however there were several shortcuts that were missing that keep me from truly navigating Gmail without a mouse. With this greasemonkey script I no longer need my mouse. I can do things such as:

• Shift + x + u - Select all unread items.

• g + label name - Navigate to a label.

• l + label name - Apply a label to an email.

• / to perform a search.

• t - trash a conversation.

Pressing h will display a help screen to show all of the options, which is displayed using the same Quicksilver style window that Google Reader uses when navigating labels. Just another way to speed up your day.

• N - View the next post.
• P - View the previous post.
• M - Mark / Unmark a post as read.

Yesterday I decided to organize my subscriptions as my list was getting a little unruly and appeared cluttered when I would sign in. Google Reader supports tags/folders so I was able to cleanly organize my feeds. Now I was faced with using the mouse again to navigate between folders (yuck!). A little research on the Google Reader docs found these little gems:

• G + L - Display a transparent window listing your tags/folders and allow you to select one via arrow keys or typing the first few letters of the folder name.
• Shift + X - Expand / Collapse selected folder.
• Shift + J - Move to next item in tree.
• Shift + K - Move to previous item in tree.
  

If you haven't given Google Reader a try I would highly recommend it, I especially like that the mobile version will sync what I've read.

I mentioned in a previous post how to add a context menu for invoking MSBuild against any .*proj file. The only problem I had was I wasn't able to pass the file name to MSBuild, which would have typically been qualified with "%1" following the MSBuild command. When MSBuild is invoked and a file isn't passed to it, it searches the directory to find one. The problem is, if there are more than one .*proj files in the same directory, it doesn't know which file to run. To solve this, I moved the setting of the environment variables to the AutoRun key of the command prompt, this way, the environment variables are always set. Then I only had to invoke MSBuild from my command entry in which I was able to pass the selected file. Here are the two registry entries needed.