README: Using a `repo_name` instead of `foo`

I get lost within all of those meaningless names.
It is useful to give things meaningful names, especially in documentation.

typo `that you cat track` -> `that you can track`

fix issue 125 and some printf vulnerabilities

typo: "availabile.d" to "available.d"

Closes https://github.com/RichiH/vcsh/issues/125



Signed-off-by: Thorsten Glaser <tg@mirbsd.org>

This reverts commit 056f86ae.

Conflicts:
	vcsh.1

This messes too much with my Debian packaging workflow; I will introduce
a new branch with static manpages (basically what I did for homebrew).

Closes https://github.com/RichiH/vcsh/issues/125



Signed-off-by: Thorsten Glaser <tg@mirbsd.org>

Never pass user input as first argument of printf(1),
similar to how you never do that with printf(3).

Signed-off-by: Thorsten Glaser <tg@mirbsd.org>

Never pass user input as first argument of printf(1),
similar to how you never do that with printf(3).

Signed-off-by: Thorsten Glaser <tg@mirbsd.org>

Suggest shorter form of vcsh pull

_vcsh: add missing commands

Fix ticks and commas

sh-code portability improvements and fixes

use export without assignment

delete needless quoting (after case, in assignments, ...)

add missing quoting (on the echo command line, ...)

make sure 'test =' is not called with empty arguments

do not call test with more than 4 arguments

Link to doc files

GitHub markdown supports linking to relative files.

Hopefully, this makes vcsh less scary

Fix a typo and some casing