zsh-users
 help / color / mirror / code / Atom feed
From: DervishD <zsh@dervishd.net>
To: Meino Christian Cramer <Meino.Cramer@gmx.de>
Cc: zsh-users@sunsite.dk
Subject: Re: Asking ZSH: How are you ?
Date: Sat, 9 Jul 2005 17:17:36 +0200	[thread overview]
Message-ID: <20050709151736.GA382@DervishD> (raw)
In-Reply-To: <20050709.165213.74740823.Meino.Cramer@gmx.de>

    Hi Meino :)

 * Meino Christian Cramer <Meino.Cramer@gmx.de> dixit:
>        When listing options (*** by `setopt', `unsetopt', `set -o' or
>        `set +o'***), those turned on by default appear in the list
>        prefixed with `no'.  Hence (unless KSH_OPTION_PRINT is set),
>        `setopt' shows all options whose settings are changed from the
>        default.
> 
>   but giving "setopt +o" or "setopt -o"
>   always gives me (even for setopt +o!):
> 
> 	   setopt: string expected after -o

    Of course it does, it's correct ;) You're mixing 'set +o/-o' with
'setopt' and 'unsetopt'. If you want to list all options use
'setopt', without arguments, or 'set -o'. If you want to show ALL
options, no matter if they have their default value or not, use this
little snippet (for example):

    for option in ${(ko)options}; print ${(r:21:}option $options[$option]

    This will give you the list of all option names followed by its
value. I find this easier to understand that the default of prefixing
with 'no' and the like.

    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...


  reply	other threads:[~2005-07-09 15:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09 14:52 Meino Christian Cramer
2005-07-09 15:17 ` DervishD [this message]
2005-07-09 15:37   ` Meino Christian Cramer
2005-07-09 16:06     ` Christian Taylor
2005-07-09 17:35       ` DervishD
2005-07-09 17:32     ` DervishD
2005-07-09 18:10       ` Meino Christian Cramer
2005-07-09 20:26   ` Thorsten Kampe
2005-07-10  7:18     ` DervishD
2005-07-10 11:38       ` Thorsten Kampe
2005-07-10 16:26         ` Bart Schaefer
2005-07-11 18:27           ` Meino Christian Cramer
2005-07-09 16:07 ` Bart Schaefer
2005-07-10  4:30   ` Meino Christian Cramer
2005-07-10 16:12     ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050709151736.GA382@DervishD \
    --to=zsh@dervishd.net \
    --cc=Meino.Cramer@gmx.de \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).