From: Larry Schrof <larrys@fb.com>
To: Bart Schaefer <schaefer@brasslantern.com>,
"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: Can we have an additional output option for setopt?
Date: Thu, 19 Jan 2012 18:37:25 +0000 [thread overview]
Message-ID: <CB3DA2D6.35C9%larrys@fb.com> (raw)
In-Reply-To: <120119094118.ZM32561@torch.brasslantern.com>
Thanks everyone - this has all been helpful, and just what I need.
On 1/19/12 9:41 AM, "Bart Schaefer" <schaefer@brasslantern.com> wrote:
>On Jan 18, 10:08pm, Mikael Magnusson wrote:
>}
>} printf '%s\t%s\n' ${(kv)options
>
>Even better:
>
>printf '%-20s %s\n' ${(kv)options}
>
>--
>Barton E. Schaefer
prev parent reply other threads:[~2012-01-19 18:56 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
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 [this message]
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=CB3DA2D6.35C9%larrys@fb.com \
--to=larrys@fb.com \
--cc=schaefer@brasslantern.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).