From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: Tee and file redirections are very slow to write anything.
Date: Wed, 24 Feb 2021 20:59:52 +0000 [thread overview]
Message-ID: <DB7PR02MB3996787E6CC91563DEB4F565E79F9@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <87eeh5b39n.fsf@Otto.invalid>
[-- Attachment #1.1.1: Type: text/plain, Size: 774 bytes --]
On 24/02/2021 20:48, ASSI wrote:
> Hamish McIntyre-Bhatty via Cygwin writes:
>> I found recently when trying to save output from a script for later
>> inspection that "tee" and file redirections seem to have massive
>> delays when run in Cygwin - usually nothing is written to file or
>> stdout until after the command has finished - not very helpful.
> You will want to switch from fully buffered to line-buffered or even
> unbuffered output.
>
>
> Regards,
> Achim.
Thanks for the prompt response.
How do I do that? Also, considering that I've never had this issue on
anything except Cygwin (various Linux distros over the years, and macOS,
with a variety of different shells), is there a reason line or no
buffering isn't the default?
Hamish
[-- Attachment #1.1.2: OpenPGP_0x18F1759B3457223F.asc --]
[-- Type: application/pgp-keys, Size: 3175 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-02-24 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 20:33 Hamish McIntyre-Bhatty
2021-02-24 20:48 ` ASSI
2021-02-24 20:59 ` Hamish McIntyre-Bhatty [this message]
2021-02-24 21:58 ` Eliot Moss
2021-02-24 22:41 ` Duncan Roe
2021-02-24 23:26 ` Takashi Yano
2021-02-25 3:54 ` Eliot Moss
2021-02-24 23:50 ` Brian Inglis
2021-02-25 7:50 ` Brian Inglis
2021-02-25 9:21 ` Hamish McIntyre-Bhatty
2021-02-25 9:51 ` Henry S. Thompson
2021-02-25 10:27 ` Takashi Yano
2021-04-18 18:45 ` Hamish McIntyre-Bhatty
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=DB7PR02MB3996787E6CC91563DEB4F565E79F9@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).