From: Felipe Contreras <felipe.contreras@gmail.com> To: Git <git@vger.kernel.org> Subject: git-completion 1.2 released Date: Thu, 19 Nov 2020 10:09:26 -0600 Message-ID: <CAMP44s1uMwRb=0rmU48R7F5GsDkHz5M0WubmnfaMgAtJRYzC0A@mail.gmail.com> (raw) Hello, Git-completion is a friendly fork of the official Git completion and prompt scripts for Zsh and Bash. The main goal is to provide a more up-to-date completion for Zsh (I'm the developer), which is basically just a wrapper around the Bash completion. Compared to Git upstream, you get many benefits for Zsh, for example: no extra unnecessary spaces, correct auto suffix removal, colors without PROMPT_COMMAND, custom aliases, fixed --no-options, and many more. There's also benefits for Bash users too, mainly plenty of bug fixes. If you use the official Zsh completion the main benefit is that it's blazingly fast. Simply doing "git log <tab>" on the Linux kernel (with 3k+ refs) takes several seconds on the official Zsh completion (about 3 seconds on my machine), with git-complete it's *instantaneous*. There's other benefits too. Since the Bash completion is actively maintained by Git developers, everything works as they intend too. For example "git send-email <tab>" correctly completes branches, as opposed to files in the Zsh official completion. Also, complex aliases such as '!f () { }; f' are correctly identified and completed out-of-the-box. It's a sister project of the Oh My Zsh gitfast plugin [2], which I maintain too. Since the last version a testing framework was added, and now all the completion tests of the Git project pass with the Zsh wrapper too [3]. For installation instructions, and more information, check the wiki [1], but basically. * make install * fpath=(~/.local/share/git-completion/zsh $fpath) Enjoy. Cheers. [1] https://github.com/felipec/git-completion/wiki/Zsh [2] https://github.com/ohmyzsh/ohmyzsh/tree/master/plugins/gitfast [3] https://travis-ci.org/github/felipec/git-completion -- Felipe Contreras
reply other threads:[~2020-11-19 16:12 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMP44s1uMwRb=0rmU48R7F5GsDkHz5M0WubmnfaMgAtJRYzC0A@mail.gmail.com' \ --to=felipe.contreras@gmail.com \ --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
git@vger.kernel.org list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ git@vger.kernel.org public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for the project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git