This should make it clearer at first glance where True and False is
referring to.

`path` is decoded already (coming from `db`) and this caused the
following error:

    Traceback (most recent call last):
      File "/home/user/.autojump/bin/autojump", line 460, in <module>
        if not shell_utility(): sys.exit(1)
      File "/home/user/.autojump/bin/autojump", line 429, in shell_utility
        results = find_matches(db, patterns, max_matches, False)
      File "/home/user/.autojump/bin/autojump", line 374, in find_matches
        if current_dir == decode(os.path.realpath(path)) :
      File "/home/user/.autojump/bin/autojump", line 277, in decode
        return text.decode(encoding, errors)
      File "/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
        return codecs.utf_8_decode(input, errors, True)
    UnicodeEncodeError: 'ascii' codec can't encode character u'\xb4' in
    position 52: ordinal not in range(128)

Instead of stating every directory to check if its realpath is the
current directory, only do so for any potential matches.

This regression bug was introduced when adding the KEEP_SYMLINKS option. The
current_dir was always set to '.' which would never match any database entries.

Closes #156.

custom installations.

Even though the previous version works fine on OS X 10.6.8, it seems to be
causing problems for other Mac users on 10.8.x. Unfortunately I do not have
access to a newer Mac to test on.

The previous test condition would cause errors because even though brew didn't
exist, the directory /share/zsh/site-functions did and it would throw error
messages on non-homebrew systems.

This adds the argparse library [1] as autojump_argparse and imports it
via sys.path mangling in case argparse does not exist (Python 2.6 or
below without argparse installed).

This makes autojump effectively work with Python 2.6 again by default.

I have not verified license compatibility, but given the intention of
the (backport) project this is likely OK (it is licensed under the
Python license).

1: http://code.google.com/p/argparse/

Fixes issue #121.

I've updated the documentation to notify end users to add compinit to their
~/.zshrc if they want tab completion.

The migration code was never working to begin with. Users migrating from v17 or
older will be starting from an empty, new database.

Forces zsh to load compinit required for tab completion.

This is to make sure we don't jump into our current directory when the symlinks
option is enabled.

Also added unit test coverage to check database initialization, saving, and
loading.  Unit tests also revealed that migration code was not working properly
(starts database from scratch instead of copying existing entries over).

--stat added, jumpstat alias removed.

Options passed to the `j` function will now be passed on autojump. As a result,
directories beginning with `-` are no longer supported.

A -s short alias for --stat is added. Instead of using jumpstat, use `j --stat`
or `j -s` instead.

As best I can tell, ZSH introduced the "=~" condition somewhere around 4.3.5 or
4.3.9. In either case, autojump will use =~ for versions higher than 4.3.5 and
  -pcre-match for older versions of ZSH.

Before zsh 4.3.5 =~ was not supported. This results in the message
'autojump.zsh:18: condition expected: =~'.