linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Bernhard Voelker" <mail@bernhard-voelker.de>,
	"Alex Henrie" <alexhenrie24@gmail.com>,
	"Christian Groessler" <chris@groessler.org>,
	"Pádraig Brady" <P@draigbrady.com>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: noloader@gmail.com, Fabrice BAUZAC <noon@mykolab.com>,
	Coreutils <coreutils@gnu.org>,
	freebsd-hackers@freebsd.org, tech@openbsd.org,
	linux-api@vger.kernel.org
Subject: Re: [PATCH] tee: Add -q, --quiet option to not write to stdout
Date: Thu, 21 Jan 2021 23:49:09 +0100	[thread overview]
Message-ID: <1f8ce444-35e2-56a7-dbd1-34e885372b11@gmail.com> (raw)
In-Reply-To: <f78ec1a9-f07f-de20-26cc-4be254e3e921@gmail.com>

[CC += mtk, linux-api, freebsd, openbsd]

On 1/21/21 10:26 PM, Alejandro Colomar (man-pages) wrote:
> Hi Berny,
> 
> On 1/21/21 10:01 PM, Bernhard Voelker wrote:
>> On 1/21/21 7:39 PM, Alex Henrie wrote:
>>> That said, I would love to see `tee -q` added to a future revision of
>>> POSIX and adopted everywhere.
>>
>> I like the idea.
>> We have been living for decades without a terminating "pipe end piece",
>> so why hurrying a new option into an implementation of 'tee'?
>> Instead, this could be discussed thoroughly and specified by the OpenGroup
>> and nailed down in a new POSIX issue, and then all implementations
>> could adopt it consistently.
>> Are you willing to start the discussion there?

Hi Berny,

Please don't feel like I'm hurrying with this.
I'm strongly defending my patch to try to
convince you that it's a Good Thing :-)
But if it has to undergo a long discussion
with POSIX, BSD, and whoever, that's fine by me.

I'll send a v2 with --silent in a moment.


Hi Michael,

Talking about designing new APIs,
you might have something to say here,
even if it's not for the kernel.


I also CCd a few lists that might be interested.
Please comment.


Cheers,

Alex

> 
> I am.  However, the Austing Group is a nightmare in terms of login,
> and doing things requiring an account; at least for me.
> 
> I'd prefer that someone else opens a bug there and links to the
> discussion on an open mailing list like this one.
> 
> Do they have an open mailing list?
> 
> Is anyone hepling me report the bug to them?  I should learn at this
> point...
> 
>>
>> BTW: --quiet is usually used to avoid outputting of informational
>> messages (e.g. wget, head, tail, md5sum), while 'tee' would change
>> its functional behavior.
>> Maybe --drain, --drain-stdout, --discard-stdout (-d), --no-stdout (-n),
>> --elide-stdout (-e) or something similar would be more appropriate?
> 
> I stand by -q, --quiet.  Conforming to: grep. Maybe there's some other.
> 
> $ man grep 2>/dev/null | sed -n '/-q, --quiet, --silent/,/^$/p'
>        -q, --quiet, --silent
>               Quiet;  do  not  write  anything to standard output.
>               Exit immediately with zero status if  any  match  is
>               found,  even if an error was detected.  Also see the
>               -s or --no-messages option.
> 
> 
> 
>>
>> Have a nice day,
>> Berny
>>
> 
> Kind regards,
> 
> Alex
> 


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

       reply	other threads:[~2021-01-21 22:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210121131735.317701-1-alx.manpages@gmail.com>
     [not found] ` <8aa1d0b4-d2ec-7d18-120b-cae59708767c@draigBrady.com>
     [not found]   ` <424b9fb9-c740-1a2f-bd79-0b4035104698@gmail.com>
     [not found]     ` <e1a3b389-b808-92db-258d-85b60748b4dc@bernhard-voelker.de>
     [not found]       ` <06fb3df3-a956-3ec1-eadb-82fd89ec62d5@gmail.com>
     [not found]         ` <af2fb24a-a03a-35ef-c86e-545844b61a8d@groessler.org>
     [not found]           ` <CAMMLpeRSh5HKi=sJV7y=pav26EzzP-yEe0+Dgp_=mtBUhtFvaQ@mail.gmail.com>
     [not found]             ` <3bb6a134-c477-116c-182d-d6e24dc342e0@bernhard-voelker.de>
     [not found]               ` <f78ec1a9-f07f-de20-26cc-4be254e3e921@gmail.com>
2021-01-21 22:49                 ` Alejandro Colomar (man-pages) [this message]
2021-01-21 23:12                   ` [PATCH v2] tee: Add -q, --quiet, --silent option to not write to stdout Alejandro Colomar
2021-01-22 18:25                     ` Alejandro Colomar (man-pages)
2021-01-23 14:53                   ` [PATCH] " Alejandro Colomar
2021-01-24 12:18                   ` [PATCH v3 (resend)] " Alejandro Colomar
2021-01-24 16:11                     ` Teran McKinney
2021-01-24 16:22                       ` Alejandro Colomar (man-pages)
2021-01-24 17:51                     ` Otto Moerbeek
2021-01-24 17:58                       ` Theo de Raadt
2021-01-24 20:01                       ` Alex Henrie
2021-01-24 20:22                         ` Otto Moerbeek
2021-01-25  4:03                         ` Bernhard Voelker
2021-01-25 11:33                           ` Alejandro Colomar (man-pages)
2021-01-26  9:08                             ` Alejandro Colomar (man-pages)
2021-01-27  1:40                           ` Alex Henrie
2021-03-14  9:44                           ` Alejandro Colomar (man-pages)
2021-03-15 17:42                             ` Alex Henrie
2021-03-15 20:20                               ` Alex Henrie
2021-01-25 16:06                     ` Philipp-Joachim Ost

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=1f8ce444-35e2-56a7-dbd1-34e885372b11@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=P@draigbrady.com \
    --cc=alexhenrie24@gmail.com \
    --cc=chris@groessler.org \
    --cc=coreutils@gnu.org \
    --cc=freebsd-hackers@freebsd.org \
    --cc=linux-api@vger.kernel.org \
    --cc=mail@bernhard-voelker.de \
    --cc=mtk.manpages@gmail.com \
    --cc=noloader@gmail.com \
    --cc=noon@mykolab.com \
    --cc=tech@openbsd.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.
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).