Ok, thanks for the reply guys :)
Cheers,
Alf
On 22 January 2014 16:04, guns wrote:
> On Wed 22 Jan 2014 at 02:21:51PM +0100, Alf Kristian Støyle wrote:
>
> > Would be nice to be able to specify that an option "must be specified
> > in every invocation" though. I think it would lead to better e
On Wed 22 Jan 2014 at 02:21:51PM +0100, Alf Kristian Støyle wrote:
> Would be nice to be able to specify that an option "must be specified
> in every invocation" though. I think it would lead to better error
> messages, e.g. if several "mandatory" options are forgotten, they will
> be shown at onc
On 22 January 2014 13:21, Alf Kristian Støyle wrote:
> Thanks! That does explain it :)
>
> Would be nice to be able to specify that an option "must be specified in
> every invocation" though. I think it would lead to better error messages,
> e.g. if several "mandatory" options are forgotten, they
Thanks! That does explain it :)
Would be nice to be able to specify that an option "must be specified in
every invocation" though. I think it would lead to better error messages,
e.g. if several "mandatory" options are forgotten, they will be shown at
once. That is a bit of a hassle when doing it
On Wed 22 Jan 2014 at 01:48:22PM +0100, Alf Kristian Støyle wrote:
> From the documentation it seems that specifying the second part of the
> "long option" should be enough to make an argument required. So this
> minimal example should also produce errors:
>
> (def cli-options-simplified
> [["-p
