From: "SZEDER Gábor" <szeder@ira.uka.de>
To: Mark Lodato <lodatom@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org, avarab@gmail.com,
Jonathan Nieder <jrnieder@gmail.com>,
Andrew Sayers <andrew-git@pileofstuff.org>
Subject: Re: [PATCHv2] completion: make compatible with zsh
Date: Mon, 30 Aug 2010 16:19:27 +0200 [thread overview]
Message-ID: <20100830141927.GA16495@neumann> (raw)
In-Reply-To: <1282877156-16149-1-git-send-email-lodatom@gmail.com>
Hi,
On Thu, Aug 26, 2010 at 10:45:56PM -0400, Mark Lodato wrote:
> Modify git-completion.bash so that it also works with zsh when using
> bashcompinit. In particular:
>
> declare -F
> Zsh doesn't have the same 'declare -F' as bash, but 'declare -f'
> is the same, and it works just as well for our purposes.
> @@ -2372,17 +2383,22 @@ _git ()
> fi
>
> local completion_func="_git_${command//-/_}"
> - declare -F $completion_func >/dev/null && $completion_func && return
> + declare -f $completion_func >/dev/null && $completion_func && return
>
> local expansion=$(__git_aliased_command "$command")
> if [ -n "$expansion" ]; then
> completion_func="_git_${expansion//-/_}"
> - declare -F $completion_func >/dev/null && $completion_func
> + declare -f $completion_func >/dev/null && $completion_func
> fi
> }
I chose -F back then because it does not print the definition of the
completion function, so there is less stuff to throw away immediately.
However, the run-time difference seems to be barely measureable (i.e.
'time declare -f _git_config >/dev/null' vs. 'declare -F _git_config
>/dev/null' sometimes shows 0.001s difference), so I'm fine with this
change.
> @@ -2417,3 +2433,29 @@ if [ Cygwin = "$(uname -o 2>/dev/null)" ]; then
> complete -o bashdefault -o default -o nospace -F _git git.exe 2>/dev/null \
> || complete -o default -o nospace -F _git git.exe
> fi
> +
> +if [[ -z $ZSH_VERSION ]]; then
-z? I think you wanted to use -n here, like at the other places.
Nit: why "if [[ ... ]]"? FWIW "if [ ... ]" would be enough.
> + shopt () {
> + local option
> + if [ $# -ne 2 ]; then
> + echo "USAGE: $0 (-q|-s|-u) <option>" >&2
> + return 1
> + fi
> + case "$2" in
> + nullglob)
> + option="$2"
> + ;;
> + *)
> + echo "$0: invalid option: $2" >&2
> + return 1
> + esac
> + case "$1" in
> + -q) setopt | grep -q "$option" ;;
> + -u) unsetopt "$option" ;;
> + -s) setopt "$option" ;;
> + *)
> + echo "$0: invalid flag: $1" >&2
> + return 1
> + esac
> + }
> +fi
> --
> 1.7.2.2
>
next prev parent reply other threads:[~2010-08-30 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 2:45 [PATCHv2] completion: make compatible with zsh Mark Lodato
2010-08-28 10:43 ` Ævar Arnfjörð Bjarmason
2010-08-30 14:19 ` SZEDER Gábor [this message]
2010-08-31 0:55 ` Mark Lodato
2010-08-31 7:52 ` Peter Kjellerstedt
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=20100830141927.GA16495@neumann \
--to=szeder@ira.uka.de \
--cc=andrew-git@pileofstuff.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=lodatom@gmail.com \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.