Please see the installation page in this guide if you are having problems getting the QS action to work. Also, Merlin Mann has posted a nice article on his usage of this action.

Using the Action

To use the Quicksilver action, just enter text-entry mode in Quicksilver by * Activating QS using your shortcut (Control-Space or Command-Space for most of you) * Hit the dot/period key to bring up text entry

Then enter some text (see the “task shorthand” options below) and tab to the action pane in QS. Start typing “kGTD” (no quotes) and you should see the action pop up. You can always set it to a default on “k” or whatever works for you.

Task Shorthand Syntax

The syntax works as follows:

  • Task Summary > Project Name @ Context

You can leave out any of those items, but the need to be in that order for now. So you could enter:

  • Task Summary > Project Name (will go to a project, but will be inactive as it has no context) or
  • Task Summary @ Context (will go to your “default new task” location as set in kGTD Settings… “Inbox” by default, but can be “!Single Tasks” or any project name) or
  • Task Summary (goes to the default task location and has no context set)

It’s insensitive

  • The task shorthand is case insenstive ( task @ Context == task @ CONTEXT == task @ context )
  • The task shorthand is white space insenstive ( task@context = task @ context )

Project names

The task shorthand also tries to be clever about guessing parts of projects and contexts. You can type just the beginning of a project name and the task will go to the first project kGTD finds that starts with that. Thus, if you have a project named “Clean up Office” you could use: * File papers > Clean @ work I tend to prepend my projects with little shorthand codes that allow me to send tasks to them easily.

Context names

Finally, the task shorthand can also guess the context if you just enter part of it. So if you have 5 contexts that all start with mac, you can enter just the last “unique” bit of the context. Thus, if your contexts include: * mac-design * mac-write * mac-research You could use a task shorthand entry like this: * Design new logo @ design That task would be set to the “mac-design” context unless you had an entirely separate context named “design” as well.