From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: zparseopts (Re: PATCH: _urls and _rpm)
Date: Tue, 6 Jun 2000 04:08:13 +0000 [thread overview]
Message-ID: <1000606040813.ZM25973@candle.brasslantern.com> (raw)
In-Reply-To: <393C2510.5F7D3880@u.genie.co.uk>
On Jun 5, 11:09pm, Oliver Kiddle wrote:
} Subject: PATCH: _urls and _rpm
}
} It would be useful if zparseopts returned 0 only if it found the option
} specified so I didn't need to use (( $#glob )) but we'd have to decide
} how it would act with more than one option specified.
No, that's no good. The whole point of calling it zparseOPTS is that the
things it is parsing are *optional*. It returns nonzero only for things
that are real mistakes.
} +zparseopts -D -E 'g:=glob'
^ ^ Why the quotes?
} +(( $#glob )) || glob=( -g '*(^/)' )
You could use
: ${(A)=glob:=-g '*(^/)'}
instead.
What I can't decide is whether I like the behavior of emptying the array
when no matching option is found. E.g. sometimes I think I'd like to be
able to say
glob=(-g '*(^/)')
zparseopts -D -E g:=glob
and have $glob be unchanged unless a -g really was given. Then I think
about it some more and decide maybe not. Then I think about it some more
and ...
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-06-06 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 22:09 PATCH: _urls and _rpm Oliver Kiddle
2000-06-06 3:48 ` Bart Schaefer
2000-06-06 4:08 ` Bart Schaefer [this message]
2000-06-06 9:58 ` zparseopts (Re: PATCH: _urls and _rpm) Oliver Kiddle
2000-06-07 5:55 ` Bart Schaefer
2000-06-06 7:15 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=1000606040813.ZM25973@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).