From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: array with newlines preserved as literal text
Date: Tue, 2 Feb 2021 17:10:16 -0800 [thread overview]
Message-ID: <99675ebd-fb20-d50f-babf-5abfce0090fb@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMoYjExx9Oq8=L68ygrE6UHniqRqEm1csh7_SwscqZJmHA@mail.gmail.com>
On 2021-02-02 11:26 a.m., Roman Perepelitsa wrote:
>
> This is fine. You can verify that the content is as expected:
>
> print -r -- $array2
Bloody hell, it was the missing '-r' there :( the array was fine, just
improper output. Past time I knew that.
> Use `typeset -p var` to see the value of parameter `var`.
>
> typeset -p array2
Thanks I knew there was something like that but I forgot it. That's
what happens when I don't code for over a year, I forget everything.
I've been busy columnizing grep output. the 'column' command doesn't
quite do it because it takes all those '\n' that you might find in code
literally which is why I had to sort that out.
|$ g ,w4 'msg "\n' g,* ||
||
||g,32,pplain in place......................120.. ! [ "$pplain" ] &&
actionmsg "\n$msg"||
||g,32,pplain in place......................168.. ! [ "$pplain" ] &&
actionmsg "\n$msg"||
||g,33,better formatting and fix rregexp....121.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,33,better formatting and fix rregexp....169.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,34,light edits..........................104.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,34,light edits..........................152.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,35,interim..............................106.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,35,interim..............................154.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,36,g_column in place interim............107.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,36,g_column in place interim............155.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,37,g_columns in place and looks good....108.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
||g,37,g_columns in place and looks good....156.. ! [ "$bbare" ] &&
actionmsg "\n$msg"||
|
Thanks Roman
next prev parent reply other threads:[~2021-02-03 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 19:16 Ray Andrews
2021-02-02 19:26 ` Roman Perepelitsa
2021-02-03 1:10 ` Ray Andrews [this message]
2021-02-02 20:25 ` Bart Schaefer
2021-02-02 23:31 ` Ray Andrews
2021-02-03 2:21 ` Bart Schaefer
2021-02-03 19:29 ` Ray Andrews
2021-02-03 21:19 ` Bart Schaefer
2021-02-04 2:07 ` Ray Andrews
2021-02-05 2:57 ` Bart Schaefer
2021-02-04 21:55 ` Ray Andrews
2021-02-05 3:22 ` Bart Schaefer
2021-02-05 4:17 ` Ray Andrews
2021-02-05 4:24 ` 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=99675ebd-fb20-d50f-babf-5abfce0090fb@eastlink.ca \
--to=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).