Default use-package-verbose to nil
Backward compatibility with emacs-22.1

This change supports the emacs that ships with MacOS X, the last version not encumbered by GPLv3.
Merge pull request #67 from dabrahams/patch-1

Backward compatibility with emacs-22.1
fboundp is a function, not a variable

Fixes #68
Add a :demand directive, to override deferred loading (#65)
use-package: use defun as lisp-indent-function

When `use-package' is called with only one keyword it is useful to
write:

(use-package foo :init
  (progn
    ... long lines ...))

instead of

(use-package foo
  :init (progn
  	  ... *too* long lines ...))

or

(use-package foo
  :init
  (progn
    ... long lines ...))

Even when there are multiple keywords or when one never wants to format
the calls to `use-package' as in the first example the use of `defun'
does not really pose a problem.
Merge pull request #69 from tarsius/defun

use-package: use defun as lisp-indent-function
allow :mode and :interpreter to accept a string

Fixes #72.
Merge pull request #73 from aspiers/short-mode

allow :mode and :interpreter to accept a string
hyperlink functions in Comments column

Previously, only the functions in the Command column were hyper-linked.
Also clarify the meaning of the "was" entries in the Comments column.
sync README.md with doc comments in elisp

The documentation in README.md was previously identical to that
in the Commentary section of use-package.el, modulo the following
differences:

  - No elisp comment ";; " prefix
  - Code blocks indented 4 columns not 2, as required by Markdown
  - Elisp symbols marked in backtick delimiters for monospace, not
    emacs backtick/forward tick pairs.

Unfortunately due to this duplication, sometimes only one of the two
files got updated, so they got out of sync.  This commit fixes that.

Fixes #46.
fix DRY violation by only having documentation in one place

The documentation in README.md was previously identical to that
in the Commentary section of use-package.el, modulo the following
differences:

  - No elisp comment ";; " prefix
  - Code blocks indented 4 columns not 2, as required by Markdown
  - Elisp symbols marked in backtick delimiters for monospace, not
    emacs backtick/forward tick pairs.

Unfortunately due to this duplication, sometimes only one of the
two files got updated, so they got out of sync.  With us all being
human, this is likely to continue to happen as long as the
duplication exists ;-)  Therefore since most users are likely to
encounter README.md before the elisp, and bearing in mind that
Markdown is a much more flexible format for documentation than
elisp comments (richer formatting, can be exported to numerous
other formats etc.), it is better to replace the docs in
use-package.el with a pointer to the README.md.
Merge pull request #78 from aspiers/docs

Synchronise docs and then remove one copy to prevent future issues.
Merge pull request #76 from aspiers/hyperlink-all-bindings

hyperlink functions in Comments column
add 'use-package-' prefix to 'with-elapsed-timer'

Fixes #35.
fix bind-key URL (fixes #58)

Also makes a start on #32.
Merge pull request #79 from aspiers/best-practices

Start addressing some of @jaalto's submitted issues.
README.md: fix typo and punctuation
stop describe-personal-keybindings adding trailing space

When emacs is configured to highlight trailing whitespace,
the *Personal Keybindings* buffer looked pretty ugly.
This fixes that.
Fix typo