Strip excess `'`s from default prompt message

In the `prompt` function in `lib/git-hub`, the default prompt message is
specified as the default value of a `:-`-form Bash parameter expansion.

This default value was wrapped in single quotation marks (instances of
U+0027 APOSTROPHE — `'`), which were taken literally by Bash, resulting
in the prompt message displayed to the user being wrapped in these same
quotation marks — e.g.:

    > Would you like start the automated 'setup' process right now? (Do
    > it!)
    >
    > 'Press <ENTER> to continue, or <CTL>-C to exit.'

This commit deletes these quotation marks, resulting in, e.g.:

    > Would you like start the automated 'setup' process right now? (Do
    > it!)
    >
    > Press <ENTER> to continue, or <CTL>-C to exit.
Minorly correct `config-not-setup` text

Apply the following minor corrections to the text printed by the
`config-not-setup` function in `lib/git-hub`:

  - De-duplicate a duplicate “a”.
  - Change “setup”, used as an adjective, to “set up” (“setup” is a
    noun).
  - Change a “which” at the start of a sentence to “This”.
  - Add a missing “to” after a “Would you like”.
Fix typo in `setup:use-auth`

In the text displayed to the user by the `setup:use-auth` function in
`lib/git-hub.d/git-hub-setup`, the word “it” had been typo’d to “is”.

This commit fixes this typo.
Merge pull request #58 from 8573/8573/fix/text/excess-quotation-marks-around-prompt-function-default-prompt-message/1

Strip excess `'`s from default prompt message
Merge pull request #59 from 8573/8573/fix/text/config-not-setup-misc/1

Minorly correct `config-not-setup` text
Merge pull request #60 from 8573/8573/fix/text/setup-use-auth-typo/1

Fix typo in `setup:use-auth`
Make line printing more regular
Fixed #61

This uncovered a couple serious bugs. Fixed now.
Some work for #15

When you have multiple remotes. This lets you set the owner explicitly:

    git config git-hub.owner somename
@8573++ points out the config key should be github

not git-hub. Thus matching ~/.git-hub/config
Clarify new PRs’ sources and targets

In the text with which `git hub pull-request` pre-populates the pull
request message, clarify which repository and branch is the source and
which is the target.

Previously, the following (e.g.) was shown:

    > New GitHub Pull Request for
    >   repo: git@github.com:ingydotnet/git-hub
    >   branch: master

When I first saw this, I didn’t know whether this referred to the source
or target (and thus, whether I had given the correct arguments) until I
read the script.

Now, the following (e.g.) should be shown:

    > New GitHub Pull Request
    >
    > Requesting that...
    >   repo: git@github.com:8573/git-hub.git
    >   branch: 8573/clarify-new-pr-source-and-target/1
    > ...be pulled into...
    >   repo: git@github.com:ingydotnet/git-hub
    >   branch: master

Note: One may notice that the source repository resource-locator ends
with `.git` and the target repository resource-locator doesn’t. This is
just because that’s what I set as the resource-locator of my `fork`
remote; as far as GitHub cares, the `.git` extension doesn’t matter.
Merge pull request #64 from 8573/8573/clarify-new-pr-source-and-target/1

Clarify new PRs’ sources and targets
Fix for #15
Attempt to add PAGER to more commands

A single issue is often longer than a page, so the primary focus is to
support PAGER for that.
assignee is a hash
Better to exit on error

Using return was causing problems.
Fix for `git hub issue-edit` carping about value.
Add rudimentary search command
Change main doc from asciidoc to kwim

and output ReadMe in pod, since it is better model than markdown.
Got kwim to do the badge (and other nits)