From: "Oliver Kiddle" <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk
Subject: Re: problem with _arguments exclusion lists
Date: Tue, 17 Apr 2001 14:55:27 +0100 (BST) [thread overview]
Message-ID: <20010417135527.14921.qmail@web9305.mail.yahoo.com> (raw)
In-Reply-To: <200104171128.NAA05617@beta.informatik.hu-berlin.de>
--- Sven Wischnowsky <wischnow@informatik.hu-berlin.de> wrote:
> > _arguments -s '(-conf)-c+:val' '-conf' '-f'
> > after -c, it completes with the 'val' message so even after -co, it
> > can't complete -conf. I found these problems with _pine which
> > completes a number after -c.
> Yes, i was aware of that. The problem is that some programs would
> not
> continue parsing `-c...' as a possible option, while some would. I
> think I would call such programs `well-behaved'.
I think you've misunderstood me here. Are you thinking of the case
where, for the _arguments example above some programs maybe allow the
`f' option after -c as `-cf3' to mean the same as `-c3 -f'?
In a case such as _pine, after `-c', there can either be a number which
is an argument to the -c option or it could go on to complete an option
with a longer name such as -conf, -character-set etc. At the moment, it
fails to complete the latter and it should do. This was the intended
gist of my last message.
> > Maybe there would be a use here for a basic
> > completion for numbers so that it can know that -co can not be -c
> with
> > a parameter.
What I was basically getting at there is something along the lines of
[[ $PREFIX$SUFFIX = [0-9]* ]] && _message 'number'
so that after -co, it could see that the `o' doesn't match [0-9]* and
would only complete further options (such as -conf).
Oliver
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
next prev parent reply other threads:[~2001-04-17 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 14:32 Oliver Kiddle
2001-04-17 9:50 ` Sven Wischnowsky
2001-04-17 10:44 ` Oliver Kiddle
2001-04-17 11:28 ` Sven Wischnowsky
2001-04-17 13:55 ` Oliver Kiddle [this message]
2001-04-17 14:10 ` Sven Wischnowsky
2001-04-19 14:01 ` Oliver Kiddle
2001-04-20 8:31 ` Sven Wischnowsky
2001-04-23 8:59 ` Oliver Kiddle
2001-04-24 10:00 ` Sven Wischnowsky
2001-04-26 11:00 ` Oliver Kiddle
2001-04-26 12:10 ` Sven Wischnowsky
2001-04-25 7:10 ` Sven Wischnowsky
2001-04-26 13:55 Oliver Kiddle
2001-04-26 14:35 ` Sven Wischnowsky
2001-05-04 16:20 ` Oliver Kiddle
2001-05-07 11:10 ` Sven Wischnowsky
2001-05-08 11:45 ` Oliver Kiddle
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=20010417135527.14921.qmail@web9305.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).