Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: False alarm (nonomatch and cshnullglob)
- X-seq: zsh-workers 1749
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: False alarm (nonomatch and cshnullglob)
- Date: Tue, 23 Jul 1996 14:58:13 -0700
- In-reply-to: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx> "Re: False alarm (nonomatch and cshnullglob)" (Jul 23, 1:18pm)
- References: <199607231735.TAA11950@xxxxxxxxxxxxxxxxx> <960723131816.ZM3002@xxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
On Jul 23, 1:18pm, Bart Schaefer wrote:
} Subject: Re: False alarm (nonomatch and cshnullglob)
}
} } > 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.
}
} Appended is an implementation using zsh functions to wrap the builtin
} setopt/unsetopt commands.
I should have mentioned that this implementation is not suitable for use
in combination with "setopt localoptions" in shell functions. If you
use this wrapper, then your shell functions that desire localoptions need
to always use "builtin setopt".
Having the behavior itself built in to zsh would eliminate that problem.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
Messages sorted by:
Reverse Date,
Date,
Thread,
Author