From: Bart Schaefer <schaefer@brasslantern.com>
To: "Oliver Kiddle" <okiddle@yahoo.co.uk>
Cc: zsh-workers@sunsite.dk
Subject: Re: ssh completion problem
Date: Fri, 8 Feb 2002 18:26:06 +0000 (GMT) [thread overview]
Message-ID: <Pine.BSF.4.40.0202081821010.90676-100000@brasslantern.com> (raw)
In-Reply-To: <20020208094052.89650.qmail@web9307.mail.yahoo.com>
On Fri, 8 Feb 2002, [iso-8859-1] Oliver Kiddle wrote:
> Suppose that an outer tag loop separately completes several labels for
> a tag and that there is an inner tag loop for which there is a defined
> tag-order. It can't then be known in the inner loop if matches are
> added for a tag because it might be ignoring matches for a different
> label which are added after it back-tracks to the outer tags loop and
> then down to the inner loop with a new tag label. Without this
> knowledge, the inner loop can't know whether to allow tags which appear
> later in the tag-order to be completed.
>
> Using a tags loop in _combination runs in to problems with this. The
> following patch appears to work:
>
> -local sep tag style keys pats key num tmp
> +local sep tag style keys pats key num tmp expl i all ret=1
>
> + _my_accounts() {
> + _wanted hosts expl host compadd "$@" -a tmp
> + }
>
> - compadd "$@" -a tmp || { (( $+functions[_$key] )) && "_$key" "$@" }
> + _tags "$tag" "not-$tag"
> + while _tags; do
> + (( $+functions[_$key] )) &&
> + _requested "not-$tag" expl 'ignore' "_$key" "$@" && ret=0
> + _requested "$tag" expl '' _my_accounts "$@" && ret=0
> + (( ret )) || break
> + done
>
> More by luck than judgement however as looking up the tag-order with
> the my-accounts tag is clearing _comp_ignore. The little _my_accounts
> function is then needed so that we get one last _next_label loop to
> separate the hosts out again.
I tried this patch, and it doesn't seem to help. That is, if I have a
tag-order style, I get the same behavior as the old _combination: it
completes the user part of the users-hosts from my-accounts, but then
offers all possible hosts as completions for what comes after the @.
Is there something else I should be doing, or was that patch not meant
to solve my problem?
next prev parent reply other threads:[~2002-02-08 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1020205170847.ZM29675@candle.brasslantern.com>
2002-02-06 9:00 ` Oliver Kiddle
2002-02-07 1:54 ` Bart Schaefer
2002-02-08 9:40 ` Oliver Kiddle
2002-02-08 18:26 ` Bart Schaefer [this message]
2002-02-11 9:12 ` Sven Wischnowsky
2002-02-11 18:04 ` Bart Schaefer
2002-02-12 9:18 ` Oliver Kiddle
2002-02-12 13:16 ` Sven Wischnowsky
2002-02-12 15:08 ` Oliver Kiddle
2002-02-12 15:20 ` Sven Wischnowsky
2002-02-15 17:15 ` Oliver Kiddle
2002-02-18 14:28 ` Sven Wischnowsky
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=Pine.BSF.4.40.0202081821010.90676-100000@brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=okiddle@yahoo.co.uk \
--cc=zsh-workers@sunsite.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).