From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Completion/Cvs/
Date: Wed, 1 Sep 1999 14:23:59 +0200 (MET DST) [thread overview]
Message-ID: <199909011223.OAA00678@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Tanaka Akira's message of 01 Sep 1999 21:01:34 +0900
Tanaka Akira wrote:
> is27e1u11% bindkey -e; fpath=($PWD/Completion/*(/)); autoload -U compinit; compinit -D; compdef _tst tst
> is27e1u11% compconf group_matches=yes
> is27e1u11% compconf message_format='%d'
> is27e1u11% compconf description_format='%d'
> is27e1u11% _tst () { _arguments '-e+:editor:(vi)' '*::mesg:false' }
> is27e1u11% tst -e<TAB>
>
> This should complete `vi', but does not.
>
> is27e1u11% cvs <TAB>
> add commit export log release tag watchers
> admin diff history login remove unedit
> annotate edit import logout rtag update
> checkout editors init rdiff status watch
>
> Also, this should complete cvs common options addition to cvs commands.
Damn, I'm getting a bit confused...
> Reverting the hunk fix this problem. Is this correct?
No, that would make `tst a -e<TAB>' complete to `vi' again. The patch
below adds a flag that says if we left the command line parsing
because we found a non-option and we have `*::..'. Whew, I hope this
gets everything right this time ;-)
Bye
Sven
diff -u oc/Base/_arguments Completion/Base/_arguments
--- oc/Base/_arguments Wed Sep 1 13:04:49 1999
+++ Completion/Base/_arguments Wed Sep 1 14:19:38 1999
@@ -7,7 +7,7 @@
local args rest ws cur nth def nm expl descr action opt arg tmp
local single uns ret=1 soptseq soptseq1 sopts prefix line
-local beg optbeg argbeg nargbeg inopt fromrest
+local beg optbeg argbeg nargbeg inopt inrest fromrest
# Associative arrays used to collect information about the options.
@@ -500,7 +500,10 @@
line=( "$line[@]" "$ws[1]" )
[[ -n "$inopt" ]] && nargbeg=$(( beg - 1 ))
inopt=''
- [[ -z "$args[nth]" && "$rest" = \*::* ]] && break
+ if [[ -z "$args[nth]" && "$rest" = \*::* ]]; then
+ inrest=yes
+ break
+ fi
(( nth++ ))
fi
fi
@@ -537,7 +540,7 @@
optbeg="$nargbeg"
argbeg="$nargbeg"
fromrest=yes
- [[ "$def" = \*::* ]] && opt=''
+ [[ -n "$inrest" ]] && opt=''
fi
fi
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-09-01 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 12:23 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-01 11:03 Sven Wischnowsky
1999-09-01 12:01 ` Tanaka Akira
1999-09-01 9:25 Sven Wischnowsky
1999-09-01 10:35 ` Tanaka Akira
1999-08-31 15:03 Tanaka Akira
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=199909011223.OAA00678@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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://git.vuxu.org/mirror/zsh/
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).