From: dherring@ll.mit.edu
To: git@vger.kernel.org
Subject: docs and completion and dashless commands
Date: Fri, 22 Aug 2008 16:26:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.0.999999.0808221550100.11892@mojave> (raw)
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`)
I tracked down "Invoke git-repo-config directly" (March 06) and related
threads; so I somewhat understand the logic. However the notions that
moving bin/git-X to libexec/git-core/git-X somehow hides complexity for
the user or fixes problems with PATH seem misguided. Maybe there were
some other reasons I missed?
Anyway, could someone modify INSTALL to mention
contrib/completion/git-completion.bash and putting `git --exec-path` in
PATH for other shells? A man page about configuring shells for git would
also be nice. These docs might also instruct users to call git-config and
set their global username and email.
Also, with the dashless commands, it may be more appropriate to distribute
a texinfo tree than flat manpages.
Thanks,
Daniel
next reply other threads:[~2008-08-22 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 20:26 dherring [this message]
2008-08-22 21:34 ` docs and completion and dashless commands Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.0.999999.0808221550100.11892@mojave \
--to=dherring@ll.mit.edu \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).