From: Mikael Magnusson <mikachu@gmail.com>
To: Larry Schrof <larrys@fb.com>
Cc: "zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: Can we have an additional output option for setopt?
Date: Wed, 18 Jan 2012 22:08:43 +0100 [thread overview]
Message-ID: <CAHYJk3Tu8UsY5r3vnZ3P-R7hZOdheaBG2MLnQ+xLLeSUvF3Hbw@mail.gmail.com> (raw)
In-Reply-To: <CB3C697C.3530%larrys@fb.com>
On 18 January 2012 21:20, Larry Schrof <larrys@fb.com> wrote:
> I can appreciate the logic that goes into displaying the 'no' prefix in the output of setopt. (As it pertains to defaults and minimizing the amount of output.)
>
> However, I find myself often wanting to see every option listed by raw name, along with it's current state. And I don't care about the defaults; I'd like to see the list without the 'no' prefixes polluting the output.
>
> I originally set KSH_OPTION_PRINT, and got this as the first few lines of output:
>
> noaliases off
> allexport off
> noalwayslastprompt off
> alwaystoend on
> ...
>
> This is CLOSE to what I want, but what I really would like to see instead is this:
>
> aliases on
> allexport off
> alwayslastprompt on
> alwaystoend on
> ...
>
> Could we consider adding in this functionality? I'll leave it up to the devs to decide how this functionality gets turned on and off, but part of me is thinking it should maybe be an option, perhaps called 'OPTION_PRINT_VERBOSE' or something like that...
printf '%s\t%s\n' ${(kv)options
--
Mikael Magnusson
next prev parent reply other threads:[~2012-01-18 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 20:20 Larry Schrof
2012-01-18 21:08 ` Mikael Magnusson [this message]
2012-01-19 10:04 ` Peter Stephenson
2012-01-19 19:28 ` Greg Klanderman
2012-01-19 17:41 ` Bart Schaefer
2012-01-19 18:37 ` Larry Schrof
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=CAHYJk3Tu8UsY5r3vnZ3P-R7hZOdheaBG2MLnQ+xLLeSUvF3Hbw@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=larrys@fb.com \
--cc=zsh-users@zsh.org \
/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).