From: Ted Pavlic <ted@tedpavlic.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "catalin.marinas" <catalin.marinas@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [StGit PATCH] Added basic bash completion script for StGit.
Date: Thu, 22 Jan 2009 11:09:03 -0500 [thread overview]
Message-ID: <49789A1F.8010203@tedpavlic.com> (raw)
In-Reply-To: <20090122160350.GA15074@diana.vm.bytemark.co.uk>
>> I didn't see it because it is generated in the build process. :(
>
> Yeah, sorry about that. I made it that way so it would be kept
> up-to-date automatically (which works quite well, by the way).
The only downside is that it's a little harder to keep track of when the
completion script changes (e.g., when you have made your own local
changes). However, the method you use provides very *fast* completion
(as opposed to git and hg completion, which generate their keywords on
the fly and thus run relatively slowly).
HOWEVER, please see the threads (which modify the Python that generates
the script):
[StGit PATCH 1/2] Modify bash completion to support help, version, and
copyright.
[StGit PATCH 2/2] Make bash completion fail to bashdefault before
default completion.
The former thread could be implemented by making help, version, and
copyright modules like the rest of the commands, but I think this method
is fine (and it makes stg help <tab> show fewer entries).
Thanks --
Ted
--
Ted Pavlic <ted@tedpavlic.com>
Please visit my ALS association page:
http://web.alsa.org/goto/tedpavlic
My family appreciates your support in the fight to defeat ALS.
next prev parent reply other threads:[~2009-01-22 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 22:57 [StGit PATCH] Added basic bash completion script for StGit ted
2009-01-19 23:15 ` Ted Pavlic
2009-01-19 23:35 ` Ted Pavlic
2009-01-22 16:03 ` Karl Hasselström
2009-01-22 16:09 ` Ted Pavlic [this message]
2009-01-22 16:18 ` Karl Hasselström
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=49789A1F.8010203@tedpavlic.com \
--to=ted@tedpavlic.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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).