Thread (1 message) 1 message, 1 author, 2016-06-15

Re: docs and completion and dashless commands

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:45:12

dherring@ll.mit.edu writes:
First off, I'm not too keen on these dashless commands.
- We now have `man git-X` but can't run `git-X`
- A separate completion script must be installed for bash
- Lose completion for all other shells
- History expansion is complicated (e.g. `!git-push` vs `!git push`)
Please stop and leave the dead horse lie in piece.  You are more than a
year too late.
Anyway, could someone modify INSTALL to mention
contrib/completion/git-completion.bash and putting `git --exec-path`
in PATH for other shells?
And please nobody waste time on the latter.  "git-foo" form for builtins
will be removed from the filesystem eventually and at that point:

	#!/bin/sh

	PATH=$(git --exec-path):$PATH
        .. do its thing ..
        git-commit -a -m 'funny wrapper created commit'

will _stop_ working.  If somebody is starting a new script there is no
point using the form only to later update to the dashless form.
These docs might also instruct users to call
git-config and set their global username and email.
Please read the first few paragraphs of gittutorial(7).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help