public
Description: A super simple command line task list with markdown storage
Clone URL: git://github.com/andykent/fly.git
fly /
name age message
file .gitignore Fri Mar 28 16:43:57 -0700 2008 added gitignore to lose ds_store files [andykent]
file README Sat Apr 05 09:55:31 -0700 2008 Tidier command line opts, datestamps & bett... [andykent]
file Rakefile Sat Apr 05 09:55:31 -0700 2008 Tidier command line opts, datestamps & bett... [andykent]
directory bin/ Thu Mar 13 16:34:42 -0700 2008 Initial check-in [andykent]
directory lib/ Sat Apr 05 09:55:31 -0700 2008 Tidier command line opts, datestamps & bett... [andykent]
directory pkg/ Sat Apr 05 09:55:31 -0700 2008 Tidier command line opts, datestamps & bett... [andykent]
directory spec/ Thu Mar 13 16:34:42 -0700 2008 Initial check-in [andykent]
file tasks.markdown Sat Mar 29 12:19:25 -0700 2008 Feature complete 0.0.1 [andykent]
README
All About Fly
=============

Fly is a super simple rubygem for tracking tasks. Fly uses markdown as it's storage format meaning that tasks are human 
readable and totally portable.

The fly gem comes complete with a command line client for easy integration into your workflow. other methods of input 
including a web interface and textmate bundle are planned.


Currently Fly supports...
-------------------------
- new document creation
- Document title
- Tasks
- Task tagging
- Multiple contexts
- Command line viewing, filtering, adding and editing
- Time stamping


Comming soon...
---------------
- Extended Comments and notes in separate files
- Tests, tests & more tests

Any help or suggestions would be appreciated.


Config
------

Fly uses sensible defaults but if you want to modify it's behavior then it has a few optional settings.
Settings are stored in YAML format in the file '.flyconfig'.
Fly loads settings from your home directory and then the current folder.
Here is an example of the current options available...
path: "/" # a path to the file location must end with a '/'
file: stuff.markdown # the filename used for storage
default_new_context: inbox # the default context applied to new tasks that aren't targeted
default_completed_context: completed # the default context for completed tasks, when using move without a target context


Usage
-----

fly title ["A List Title"]
fly add TASK_NAME [--context CONTEXT]
fly move TASK_IDS [--context NEW_CONTEXT]
fly list [CONTEXT] [--tags TAGS]
fly count [CONTEXT] [--tags TAGS]
fly tags [CONTEXT]