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

Re: False alarm (nonomatch and cshnullglob)

X-seq: zsh-workers 1744
From: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
To: schaefer@xxxxxxx
Subject: Re: False alarm (nonomatch and cshnullglob)
Date: Tue, 23 Jul 1996 19:35:43 +0200 (MET DST)
Cc: pws@xxxxxx, zsh-workers@xxxxxxxxxxxxxxx
In-reply-to: <960723013421.ZM936@xxxxxxxxxxxxxxxxxxxxxxx> from Bart Schaefer at "Jul 23, 96 01:34:21 am"
Organization: Dept. of Comp. Sci., Eotvos University, Budapest, Hungary
Phone: (36 1)2669833 ext: 2667, home phone: (36 1) 2752368

> Someone previously suggested that options should be heirarchical, or
> somehow otherwise related, so that (e.g.) "setopt nonomatch" would
> automatically imply "unsetopt nullglob cshnullglob".

Perhaps that would be nice but I'm not sure it worth the extra code it adds.

> The advantage to csh's scheme of having magic variable names for the
> options is that you can easily convert booleans to have more than two
> values, without changing the syntax of setting options in general and
> without losing the old set/unset boolean meaning.

It would not be difficult to add the setopt option=value syntax.  Options
are stored in a char array so this can be done without changing the array.
But I still do not see how can such a feature be used.

Zoltan

References:
- Re: False alarm (nonomatch and cshnullglob)
  - From: Bart Schaefer

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