From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: triviality regarding $# counts
Date: Sat, 13 Apr 2024 08:14:12 -0700 [thread overview]
Message-ID: <a7d236f9-0a40-4fc8-ab8f-2db9ce6edda7@eastlink.ca> (raw)
In-Reply-To: <3cc19e86-e953-4e2f-9e57-30ff84f15fdf@eastlink.ca>
[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]
> I dunno. I've lost the example that I saved. Never mind, I'll keep an eye on it, and figure out next time. Red herring for now. It's a bit confusing looking into typeset -p output. All this 'splitting' stuff is not simple. For now everything works and I'm quite sure it's a bit more orthodox.
>
>
A script:
---------------------------------------------------------------------------------
redline () { echo -e "$red$@$nrm" }
typeset -ga aaa=("
abc
def ghi
jkl mno
pqr
")
redline "\naaa:"
print -l $aaa
redline "\naaa[1]:"
print -l $aaa[1]
redline "linecount of aaa is: $#aaa ... Single element!"
ccc=( ${(@f)aaa} )
redline '\nccc=( ${(@f)aaa} )'
print -l $ccc
redline "linecount of ccc is: $#ccc ... split, but blank lines gone."
ddd=( "${(@f)aaa}" )
redline '\nddd=( "${(@f)aaa}" ) ... it seems like a lot of trouble to
copy the array as it is.'
print -l "$ddd[@]" #... don't forget the quotes, idiot!"
redline "linecount of ddd is: $#ddd ... split, but blanks preserved and
counted. NB EIGHT NOT SIX!"
redline "\nddd[1]: That's right it's blank, just as it should be."
print -l $ddd[1]
redline "\nddd[2]:"
print -l $ddd[2]
redline "And now the typesets\n"
typeset -p aaa
typeset -p ccc
typeset -p ddd
# Verbatim:
# typeset -a aaa=( $'\nabc\n\n\tdef ghi\n\tjkl mno\n\n\tpqr\n' )
# typeset -a ccc=( abc $'\tdef ghi' $'\tjkl mno' $'\tpqr' )
# typeset -a ddd=( '' abc '' $'\tdef ghi' $'\tjkl mno' '' $'\tpqr' '' )
# Aligned: Note the steeenking dollars ;-) ... and how they seem to
replace the newlines. No?
# typeset -a aaa=( $'\nabc \n\n\tdef ghi \n\tjkl mno \n\n\tpqr\n'
) #Original with blanks
# typeset -a ccc=( abc $'\tdef ghi' $'\tjkl mno ' $'\tpqr' )
#No blanks.
# typeset -a ddd=( '' abc '' $'\tdef ghi' $'\tjkl mno' '' $'\tpqr' ''
) #Blanks retained BUT not the same structure!
-----------------------------------------------------------------------------------
... so what about the dollars?
Anyway, it comes clear: '${(@f)....}' doesn't ADD (or retain) newlines
it removes them! (Tho splitting the array where they used to be.)
Doesn't need them cuz elements aren't separated by newlines (like I
thought) but by ... however it's done. Single quotes indicate
elements. And, best of all, copying an array, blanks and all, (not
shown above) turns out to be simple:
eee=( $aaa ) and:
eee=( "{$(@f)aaa}" )
... turns out to be a false equivalence where newlines are REMOVED.
Don't be fooled by 'printf' -- it might not show you the genuine state
of the array. Scalars show their blank lines automatically but we need:
print -l -- "$eee[@]"
... with arrays. Trust typedef -p.
[-- Attachment #2: Type: text/html, Size: 3679 bytes --]
next prev parent reply other threads:[~2024-04-13 15:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 0:56 Ray Andrews
2024-04-12 4:55 ` Lawrence Velázquez
2024-04-12 14:48 ` Ray Andrews
2024-04-12 19:09 ` Bart Schaefer
2024-04-13 1:13 ` Ray Andrews
2024-04-13 1:33 ` Mark J. Reed
2024-04-13 2:28 ` Ray Andrews
2024-04-13 3:25 ` Lawrence Velázquez
2024-04-13 14:37 ` Ray Andrews
2024-04-13 15:14 ` Ray Andrews [this message]
2024-04-13 17:19 ` Mark J. Reed
2024-04-13 17:27 ` Mark J. Reed
2024-04-13 18:08 ` Ray Andrews
2024-04-13 19:45 ` Bart Schaefer
2024-04-13 20:36 ` Ray Andrews
2024-04-13 21:01 ` Bart Schaefer
2024-04-14 0:28 ` Ray Andrews
2024-04-14 0:30 ` Lawrence Velázquez
2024-04-14 3:26 ` Ray Andrews
2024-04-14 3:49 ` Lawrence Velázquez
2024-04-14 4:57 ` Bart Schaefer
2024-04-14 13:24 ` Ray Andrews
2024-04-14 13:35 ` Roman Perepelitsa
2024-04-14 14:06 ` Ray Andrews
2024-04-14 14:15 ` Roman Perepelitsa
2024-04-14 14:53 ` Ray Andrews
2024-04-14 15:11 ` Mark J. Reed
2024-04-14 16:23 ` Ray Andrews
2024-04-14 14:06 ` Mark J. Reed
2024-04-14 14:47 ` Ray Andrews
2024-04-14 14:59 ` Mark J. Reed
2024-04-14 15:51 ` Bart Schaefer
2024-04-14 17:22 ` Ray Andrews
2024-04-14 17:42 ` Mark J. Reed
2024-04-14 18:24 ` Bart Schaefer
2024-04-14 22:00 ` Ray Andrews
2024-04-13 20:11 ` Mark J. Reed
2024-04-13 20:53 ` Bart Schaefer
2024-04-14 0:19 ` Ray Andrews
2024-04-13 1:35 ` 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=a7d236f9-0a40-4fc8-ab8f-2db9ce6edda7@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).