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 08:55:44 -0800	[thread overview]
Message-ID: <b3c9be89-12ba-436c-b7ee-0654e7dd1dcd@eastlink.ca> (raw)
In-Reply-To: <CAN=4vMoDLBPTTUusnOMYYSwoXZZFSathUURLjKxHwzLiEqnsqQ@mail.gmail.com>

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



On 2024-02-15 08:16, Roman Perepelitsa wrote:
> My little opinion doesn't constitute a detailed proposal for change,
> nor does it represent an alternative solution that might have been
> applicable in the past. I harbor doubts about its potential to evolve
> into anything substantial, acknowledging that any such development
> would necessitate effort I'm not prepared to expend. Given the minimal
> effort I've dedicated to forming this opinion, I recognize that others
> are under no obligation to engage with or comment on it. I've aimed to
> express my thoughts modestly to accurately reflect my assessment of
> their value, though I concede I may not have fully succeeded. When you
> agree with my opinion and wish for a vote, you give it more credit
> than it deserves. It's not developed enough for either of these
> things.
Understood and taken for granted.  My own thoughts on the subject should 
be taken in the same spirit and then diminished further due to my lack 
of experience and knowledge.  It disturbs me when my comments are taken 
more seriously by others than I take them myself -- they are ... 
'investigations' is perhaps the right word.  For example I wasn't 
suggesting an actual vote, I was musing on the possibility that 
arbitrary defaults might be determined by polling users as a general 
principle.  Dunno, I'd stop doing that sort of thing entirely since some 
strongly object to it, however I do get responses which seems to 
indicate that some -- notably yourself -- find discussing such matters 
worth doing.  I myself always come out of it the wiser.  It's an 
exploration.  Take everything I say very litely.



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

  reply	other threads:[~2024-02-15 16:56 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 [this message]
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=b3c9be89-12ba-436c-b7ee-0654e7dd1dcd@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).