From: "Oliver Kiddle" <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk
Subject: Re: ssh completion problem
Date: Fri, 15 Feb 2002 17:15:32 +0000 (GMT) [thread overview]
Message-ID: <20020215171532.57115.qmail@web9302.mail.yahoo.com> (raw)
In-Reply-To: <15465.13002.262337.128763@wischnow.berkom.de>
--- Sven Wischnowsky <wischnow@berkom.de> wrote: >
> > One idea I have for solving the main part of the problem is only
> doing
> > a _next_labels loop around final compadd commands. This loop would
> need
> > to loop over all labels for every tag for which an _requested is in
> our
> > funcstack. It would lose some flexibility such as a tag-order like:
> > 'hosts:-domain users' 'hosts:-ipaddr ports'
> > no longer being possible ...
> > ... limitations so I'll be doing some further thinking.
> But interesting ideas already...
The only other solution I've thought of would be to defer all tag/label
loops until the very end after all matches are added. It'd need to
track the path of added matches building up a list of associated tags.
It would allow the mixed label/tag tag-orders like the example above
but be less efficient because unwanted matches would be generated.
I think I prefer my first idea which also has the advantage of being
closer to the current system. I don't think separate tag and label
ordering would matter much. I've still got some lines of thought I want
to follow though.
If the tags dependence on funcstack to track nested tags loops goes, we
may need to act on a tag loop exiting. Currently, we break out of the
loops with `(( ret )) || break'. Can't that be done with a
compstate[nmatches] test in _tags - I'd prefer if we didn't have to set
and test $ret there anyway.
> > I'd have expected an _requested if around the _next_label prefixes
> loop
>
> That's only needed when there are two or more possible tags. If the
> only tag offered isn't wanted by the user the _tags in the while loop
> never returns non-zero (and hence we don't really need a loop there).
Ah, that explains.
> > and an _next_labels loop inside the _requested urls if. I thought
> > _requested only used _all_labels if it got description arguments.
>
> That's left to the _wanted, _newsgroups and that _tags-loop, it
> seems.
Okay, but those _wanted calls use a different tag. Labels setup for the
urls tag might not then be handled.
Cheers
Oliver
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
next prev parent reply other threads:[~2002-02-15 17:15 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
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 [this message]
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=20020215171532.57115.qmail@web9302.mail.yahoo.com \
--to=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).