From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: triviality regarding $# counts
Date: Sat, 13 Apr 2024 11:08:31 -0700 [thread overview]
Message-ID: <0a0b9ec3-4661-4386-9fbf-b3152a46001e@eastlink.ca> (raw)
In-Reply-To: <CAA=-s3x6B5rrNJ-YmVOEspXrhW-4G-6u=1jFmocYCNDzHqAkdg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On 2024-04-13 10:27, Mark J. Reed wrote:
> Small followup I meant to type but didn't:
>
> On Sat, Apr 13, 2024 at 1:19 PM Mark J. Reed <markjreed@gmail.com> wrote:
>
> redline *'\nddd=( "${(@f)aaa}" ) ... it seems like a lot of
> trouble to copy the array as it is.'*
>
>
> That comment confuses me; you aren't copying the array as it is at
> all! You've gone from *aaa, *which has one element, to *ddd
> *having 8 elements. That's a far cry from "copying as it is".
>
Ah, but Mark, I figured all that out by the bottom of the post. At that
point I was still laboring under 'visual thinking' . I dare say I'm
straightened out. I had thought that 'split on newlines' meant 'add
\n's where needed to demarcate element boundaries'. It's actually sorta
the opposite -- there is no demarcation character and \n's will in fact
be removed. But I'm still not happy with the dollars. I had thought
that " $'...' " was grammatical but we have " ' ' " -- meaning an
empty line -- without the leading dollar, so the closest thing I could
pattern was that they replaced the newlines. If anyone on the planet
can get it wrong, it's me.
[-- Attachment #2: Type: text/html, Size: 3114 bytes --]
next prev parent reply other threads:[~2024-04-13 18:09 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
2024-04-13 17:19 ` Mark J. Reed
2024-04-13 17:27 ` Mark J. Reed
2024-04-13 18:08 ` Ray Andrews [this message]
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=0a0b9ec3-4661-4386-9fbf-b3152a46001e@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).