If `git foo` exits 13, it would be prudent for vcsh to exit 13, as well.
Start with support for `vcsh pull`.

GitHub: fixes RichiH/vcsh#104

Add hooks to allow fancy merge handling

Cloning a repo over an existing set of files would usually
cause a merge conflict that aborts the process and requires
manual intervention. This pair of hooks handles that case
by manually moving the extant objects out of the way,
completing the checktout, then restoring them to their
original places. The resulting state is a set of unstaged
local changes.

These hooks before and after the actual checkout process
will enable a pair of hook scripts to automatically handle
conflicts and potentially allow the checkout of repositories
over existing file sets

By replacing the "for" loop with a "while" loop, it is easy to read
line-oriented output without worrying about spaces. However, now the
loop executes in a subshell, and VCSH_CONFLICT won't be available in
the parent shell. In this case, a trivial, portable solution is to
have the comparison as the last command in the subshell.

`vcsh clone` does:

    VCSH_REPO_NAME=$(basename "${GIT_REMOTE}" .git)

Typically, most remote paths will have a non-empty directory component,
so using basename works well in all common cases. However, when doing
something like:

    % vcsh clone example.org:repo.git

VCSH_REPO_NAME will be set to "example.org:repo" instead of "repo". This
also happens when using url.<x>.insteadOf, à-la:

    % vcsh clone v:repo

Stripping everything up to the first colon in the remote URL fixes the
issue.

N.B.: remote URLs with protocol (e.g. http://, git://, or ssh://) do
not exhibit this problem, and are unaffected by this change.

Conflicts:
	vcsh

Configurations and other dotdir content may be highly confidential.

Ensure we're not leaking/exposing information by making vcsh
repositories user-accessible, only.

Thanks to Enrico Zini for realizing this was a problem.

Opening Vim in $PWD without a file name (think scratch pad) will open
.swp, which is not matched by *.swp

Add Gentoo installation in README

2650689d introduced a bug:
If we are using a template, GNU mktemp will use PWD instead of $TMPDIR

Use printf, not echo -n to print messages without newline

OS X echo does not understand -n and prints it literally

README.md: Use GFM tables for Usage

Table syntax in GFM?  Oh, yes: 
<https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#tables>

This reverts commit 794f0aac.

Conflicts:
	vcsh

Turns out the shell implementation didn't account for trailing
slashes. While, arguably, a proper interactive shell should eat
them before execution anyway, this can also be called in script
context.

This means that

    vcsh clone foo/

made it fail and even after commit 7e33e38a

    vcsh clone foo//

would have failed.

Revert to safe and time-proven default: Standalone `basename`.

For further information, see:

https://github.com/RichiH/vcsh/pull/92

If the repository path given to 'vcsh clone' contains a trailing slash,
the resulting cloned directory will be '.git' and vcsh will not
recognize the cloned repository by name. This change ensures that a
trailing slash will be stripped and the repository name will be
populated.

The previous faulty behavior is due to the custom implementation of the
basename command first introduced in 794f0aac.