From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: The elements of enlightenment
Date: Mon, 5 Dec 2022 17:24:05 +0100 [thread overview]
Message-ID: <CAN=4vMp2r4Syu-CuF=gxed5om9JQ+NDQm6LvNZRBE4d5a4v1xw@mail.gmail.com> (raw)
In-Reply-To: <54bcd6dd-e589-4696-f042-1155b78df9d2@eastlink.ca>
On Mon, Dec 5, 2022 at 4:58 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> I think I've finally actually figured out the reason that lines aren't
> elements and elements aren't lines even though they can print exactly
> the same:
>
> $ list=( $( setopt ) )
This is the standard way of splitting the output of a command into
lines and dropping empty lines:
list=( ${(f)"$(setopt)"} )
This requires KSH_OPTION_PRINT, just like your code. It may not be the
best idea to write code that deals with options in a way that requires
specific options.
It's unlikely that you need to capture the output of setopt in the
first place given that there is $options associative array.
() {
local k v
local -A color=(on 32 off 33)
for k v in ${(kv)options}; do
printf '%-20s = \e[%sm%s\e[0m\n' $k ${color[$v]} $v
done
}
Dealing with options as an associative array is a lot easier than
dealing with text.
Roman.
next prev parent reply other threads:[~2022-12-05 16:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 15:57 Ray Andrews
2022-12-05 16:24 ` Roman Perepelitsa [this message]
2022-12-05 18:30 ` Bart Schaefer
2022-12-05 19:35 ` Ray Andrews
2022-12-05 19:44 ` Bart Schaefer
2022-12-05 19:58 ` Roman Perepelitsa
2022-12-05 21:20 ` Ray Andrews
2022-12-05 21:49 ` Roman Perepelitsa
2022-12-05 23:52 ` Ray Andrews
2022-12-06 0:17 ` Bart Schaefer
2022-12-06 1:34 ` Ray Andrews
2022-12-06 18:55 ` Roman Perepelitsa
2022-12-06 19:45 ` Bart Schaefer
2022-12-06 20:01 ` Roman Perepelitsa
2022-12-06 20:07 ` Bart Schaefer
2022-12-06 20:22 ` Roman Perepelitsa
2022-12-06 23:52 ` Lawrence Velázquez
2022-12-07 1:04 ` Lawrence Velázquez
2022-12-05 21:49 ` Bart Schaefer
2022-12-05 21:51 ` Bart Schaefer
2022-12-05 22:24 ` Ray Andrews
2022-12-05 23:24 ` Bart Schaefer
2022-12-06 1:47 ` Ray Andrews
2022-12-06 6:39 ` Lawrence Velázquez
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='CAN=4vMp2r4Syu-CuF=gxed5om9JQ+NDQm6LvNZRBE4d5a4v1xw@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=rayandrews@eastlink.ca \
--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).