From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 96d87dcb for ; Thu, 7 Feb 2019 18:56:35 +0000 (UTC) Received: (qmail 11157 invoked by alias); 7 Feb 2019 18:56:21 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 44056 Received: (qmail 28543 invoked by uid 1010); 7 Feb 2019 18:56:21 -0000 X-Qmail-Scanner-Diagnostics: from granite.fifsource.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.100.2/25112. spamassassin: 3.4.2. Clear:RC:0(173.255.216.206):SA:0(-1.9/5.0):. Processed in 1.96103 secs); 07 Feb 2019 18:56:21 -0000 X-Envelope-From: phil@fifi.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Message-ID: <08a8c442d9d467bd64da9e613beca22f2d80e2fa.camel@fifi.org> Subject: Re: Could multios response positively to isatty(1) test? From: Philippe Troin To: zsh-workers@zsh.org Date: Thu, 07 Feb 2019 10:56:14 -0800 In-Reply-To: References: <1549551768.5863.1.camel@samsung.com> <1549558209.5863.7.camel@samsung.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.4 (3.30.4-1.fc29) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit On Thu, 2019-02-07 at 18:55 +0100, Sebastian Gniazdowski wrote: > On Thu, 7 Feb 2019 at 17:50, Peter Stephenson < > p.stephenson@samsung.com> wrote: > > > > isatty() is part of the operating system, it doesn't have a way of > > checking for "not a real TTY but pretending to be one except > > actually it > > isn't really even pretending to be one but it might work anyway" > > Yes it's a part of the operating system, and i wonder how it works? I > suspect that there's just a flag needed to be set on the FD exposed > to > the application. It boils down to ioctl(TCGETS) on linux if you have to know. It the same ioctl as the one used for tcsetattr/tcgetattr. Have you tried: script -c "scrapy crawl $options[@]" log.txt Phil.