zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Counting characters in command output?
Date: Thu, 15 Feb 2024 06:53:42 -0800	[thread overview]
Message-ID: <aa32668a-330a-4de5-b2b8-183ea0ad30d6@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMop_MyF0jyVq14Jd1TXRked9vmeUxOK+xXjPMJGnM0UBg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]


On 2024-02-15 01:50, Roman Perepelitsa wrote:
> In any debate between tradition and helpfulness, ensure your
> counterpart agrees with this perspective. Should they present
> arguments they consider essential for necessity and consistency, and
> you categorize them merely as "tradition," dialogue ceases. From their
> standpoint, your stance appears at best inconsistent, or at worst,
> vague, and you fail to recognize their points even when clearly
> outlined.
Sure.  Nobody wins a debate like that automatically.  In this case I 
agree with yourself and Mark, and I'm just saying why.  If my arguments 
(or yours or Mark's) fail to persuade then they go nowhere.  As for me, 
I'm wrong more often than I'm right.  Like that last thing -- I got my 
brain twisted into a pretzel and it took Mark to straighten me out 
privately.  (I was actually going to apologize to the list but didn't 
want to waste even more keystrokes.)
>
> For anything to happen, somebody has to do the work. There is no point
> in voting if the vote has no consequences: it's not an obligation for
> anybody to do the work, nor does any work require an approval from
> voters.
Yeah, it's the ultimate worker's paradise -- if someone thinks something 
is worth doing it might just get done.  Still, when a default could be 
considered arbitrary, one might inquire of the masses which they'd 
prefer.  And I think you and Mark are correct on that point.
> Compare what Bart has done to my posting an opinion on this thread.
> One is work, and thus has impact, the other isn't and remains
> inconsequential.
Unless the devs take your point, and implement it.  Talk precedes work 
and good talk makes for good work.


[-- Attachment #2: Type: text/html, Size: 2517 bytes --]

  parent reply	other threads:[~2024-02-15 14:55 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
2024-02-15 16:16               ` Roman Perepelitsa
2024-02-15 16:55                 ` Ray Andrews
2024-02-15 14:53           ` Ray Andrews [this message]
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=aa32668a-330a-4de5-b2b8-183ea0ad30d6@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).