Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Asking ZSH: How are you ?
- X-seq: zsh-users 9087
- From: Thorsten Kampe <thorsten@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Asking ZSH: How are you ?
- Date: Sun, 10 Jul 2005 12:38:30 +0100
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20050709.165213.74740823.Meino.Cramer@xxxxxx> <20050709151736.GA382@DervishD> <m6b6fm1b79y7.13jinvogu8q6.dlg@xxxxxxxxxx> <20050710071800.GA583@DervishD>
- Sender: news <news@xxxxxxxxxxxxx>
* DervishD (2005-07-10 08:18 +0100)
> * Thorsten Kampe <thorsten@xxxxxxxxxxxxxxxx> dixit:
>>> for option in ${(ko)options}; print ${(r:21:}option $options[$option]
>> Isn't that a bit "too much"?
>>
>> "autoload -U allopt; allopt" or "set -o" shows you all options and
>> there state.
>
> Have you looked at the code for 'allopt'? I think that *that* is
> too much ;)
Maybe for the one who wrote it but not for the one who uses allopt.
"allopt" was the way to go before "set -o" was introduced recently.
Before that you had to do "setopt kshoptionprint; setopt; unsetopt"
which of course in a way was inaccurate because "kshoptionprint" was
modified.
T.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author