From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Counting characters in command output?
Date: Thu, 15 Feb 2024 07:29:17 -0800 [thread overview]
Message-ID: <0e4efb91-0a73-4da3-a7a1-d5bce58ae914@eastlink.ca> (raw)
In-Reply-To: <c71b3dca-d39d-4e2f-98e7-34a22295a48b@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
On 2024-02-15 06:30, Lawrence Velázquez wrote:
> I would push it further: The worst-case perception would be one of ignorant arrogance. Compatibility is not tradition, but calling it so suggests a dismissive, uncharitable belief that there are no plausible reasons for it -- only a stubborn preference for How Things Used to Be. People rarely respond well when they think they're being called sclerotic morons.
On the contrary, compatibility is deference to tradition almost by
definition. However it does not follow that tradition is to be
deprecated or dismissed -- long standing traditions often stand long
because they deserve to, and compatibility is a value in itself -- one
breaks compatibility only if some practical advantage clearly merits the
added confusion of incompatibility. In this case Mark had an issue,
Roman agreed that the default was not optimal, and I'm agreeing with
them. Your hostility seems overwrought. Voting is a poor mechanism for
building consensus, in any case.
> https://producingoss.com/en/consensus-democracy.html#when-to-vote
Interesting!
% foo=(a b c)
% printf '<%s>' $foo; echo
<a><b><c>
% bar=$foo
% printf '<%s>' $bar; echo
<a b c>
Ok, but:
% foo=(a b c);printf '<%s>' $foo; echo; bar=($foo); printf '<%s>' $bar; echo
^ ^
<a><b><c>
<a><b><c>
... it is established that the assignment must be forced to array and will default to scalar, no? Sure, it's not exactly algebra but it is bedrock zsh grammar. And wasn't it Mark's original point that command substitution should likewise default to scalar?
Anyway these probings of mine bother you so perhaps I should say nothing.
[-- Attachment #2: Type: text/html, Size: 2624 bytes --]
next prev parent reply other threads:[~2024-02-15 15:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 20:38 Mark J. Reed
2024-02-13 20:41 ` Roman Perepelitsa
2024-02-14 0:45 ` Mark J. Reed
2024-02-14 6:49 ` Roman Perepelitsa
2024-02-14 13:56 ` Mark J. Reed
2024-02-14 15:36 ` Ray Andrews
2024-02-14 15:58 ` Mark J. Reed
2024-02-14 16:30 ` Ray Andrews
2024-02-15 14:34 ` Lawrence Velázquez
2024-02-15 9:50 ` Roman Perepelitsa
2024-02-15 14:30 ` Lawrence Velázquez
2024-02-15 15:29 ` Ray Andrews [this message]
2024-02-15 16:16 ` Roman Perepelitsa
2024-02-15 16:55 ` Ray Andrews
2024-02-15 14:53 ` Ray Andrews
2024-02-16 1:53 ` Bart Schaefer
2024-02-16 4:53 ` Lawrence Velázquez
2024-02-16 18:03 ` Bart Schaefer
2024-02-16 18:38 ` Mark J. Reed
2024-02-16 19:36 ` Bart Schaefer
2024-02-16 19:37 ` Lawrence Velázquez
2024-02-16 21:06 ` Mikael Magnusson
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=0e4efb91-0a73-4da3-a7a1-d5bce58ae914@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).