From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
"SZEDER Gábor" <szeder@ira.uka.de>,
"Matthieu Moy" <matthieu.moy@grenoble-inp.fr>,
"Felipe Contreras" <felipe.contreras@gmail.com>
Subject: [PATCH v6 0/3] completion: refactor and zsh wrapper
Date: Mon, 22 Oct 2012 03:45:39 +0200 [thread overview]
Message-ID: <1350870342-22653-1-git-send-email-felipe.contreras@gmail.com> (raw)
Hi,
Here's a bit of reorganition. I'm introducing a new __gitcompadd helper that is
useful to wrapp all changes to COMPREPLY, but first, lets get rid of
unnecessary assignments as SZEDER suggested.
The zsh wrapper is now very very simple.
Since v5:
* Get rid of unnecessary COMPREPLY assignments
Felipe Contreras (3):
completion: get rid of empty COMPREPLY assignments
completion: add new __gitcompadd helper
completion: add new zsh completion
contrib/completion/git-completion.bash | 41 ++++++-----------------------
contrib/completion/git-completion.zsh | 48 ++++++++++++++++++++++++++++++++++
2 files changed, 56 insertions(+), 33 deletions(-)
create mode 100644 contrib/completion/git-completion.zsh
--
1.8.0
next reply other threads:[~2012-10-22 1:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 1:45 Felipe Contreras [this message]
2012-10-22 1:45 ` [PATCH v6 1/3] completion: get rid of empty COMPREPLY assignments Felipe Contreras
2012-10-22 1:45 ` [PATCH v6 2/3] completion: add new __gitcompadd helper Felipe Contreras
2012-10-30 22:58 ` SZEDER Gábor
2012-10-30 23:05 ` Felipe Contreras
2012-10-31 14:15 ` SZEDER Gábor
2012-10-22 1:45 ` [PATCH v6 3/3] completion: add new zsh completion Felipe Contreras
2012-10-30 16:15 ` [PATCH v6 0/3] completion: refactor and zsh wrapper Felipe Contreras
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=1350870342-22653-1-git-send-email-felipe.contreras@gmail.com \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=matthieu.moy@grenoble-inp.fr \
--cc=peff@peff.net \
--cc=szeder@ira.uka.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).