Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: getopts and long options

X-seq: zsh-users 9356
From: DervishD <zsh@xxxxxxxxxxxx>
To: Zsh Users <zsh-users@xxxxxxxxxx>
Subject: Re: getopts and long options
Date: Tue, 30 Aug 2005 16:20:45 +0200
In-reply-to: <20050830135522.GA30705@xxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Zsh Users <zsh-users@xxxxxxxxxx>
Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
Organization: DervishD
References: <20050830101604.GA14851@DervishD> <20050830135522.GA30705@xxxxxxxxxxxxxxxxxxxxx>

    Hi Doug :)

 * Doug Kearns <dougkearns@xxxxxxxxx> dixit:
> On Tue, Aug 30, 2005 at 12:16:04PM +0200, DervishD wrote:
> >     I would prefer to use the "getopts" builtin if possible, rather
> > than GNU getopt, to avoid a dependency, so: is there any 'trick' for
> > "getopts" to make it accept long options or must I use GNU getopt?
> Have a look at zparseopts.

    I think I've already told in this list that sometimes (quite
frequently, lately) I'm a dumbass. Well, in my defense I'll say that
I thought that zparseopts was a contribution script and I don't
wanted to ship my script with a dependency on another script. But it
is a builtin and I'm a dumbass...

    Thanks for pointing, Doug, otherwise I would have written a
parser for long options or used GNU getopt O:) Thanks a lot, really.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...

References:
- getopts and long options
  - From: DervishD
- Re: getopts and long options
  - From: Doug Kearns

Messages sorted by: Reverse Date, Date, Thread, Author