From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13464 invoked by alias); 14 Aug 2018 21:51:27 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 23582 Received: (qmail 20218 invoked by uid 1010); 14 Aug 2018 21:51:27 -0000 X-Qmail-Scanner-Diagnostics: from mta04.eastlink.ca by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(24.224.136.10):SA:0(-2.6/5.0):. Processed in 3.563842 secs); 14 Aug 2018 21:51:27 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_PASS autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: rayandrews@eastlink.ca X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=utf-8; format=flowed X-Authority-Analysis: v=2.3 cv=R/q35uZX c=1 sm=1 tr=0 a=RnRVsdTsRxS/hkU0yKjOWA==:117 a=RnRVsdTsRxS/hkU0yKjOWA==:17 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=gir0-LH0AAAA:8 a=vDG3BvN9itEolrkUVxgA:9 a=QEXdDO2ut3YA:10 a=aLewGyoHDmJ4ULJHWpSz:22 X-EL-IP-NOAUTH: 24.207.101.9 Subject: Re: ticking clock To: zsh-users@zsh.org References: <1534170704.3055908.1472497128.24A0E402@webmail.messagingengine.com> <5d1d108b-d65d-9c5b-64fa-017d3a9637a8@eastlink.ca> <84b1dcba-fa72-140e-1733-c31430bf1b41@eastlink.ca> From: Ray Andrews Message-id: <5c13aae7-ddd8-8f2f-a818-f38dba14150f@eastlink.ca> Date: Tue, 14 Aug 2018 14:21:15 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 In-reply-to: Content-language: en-CA On 14/08/18 10:27 AM, Bart Schaefer wrote: > On Mon, Aug 13, 2018 at 3:45 PM, Ray Andrews wrote: >> So no way to have it tick only when it's idle, and never force a scroll? > The terminal emulator doesn't "inform" the shell when you scroll back, > so there's no way for the shell to know that it should stop sending > output. Right , so the prompt doesn't even know if it's visible.  And I can see that it's no small thing for the shell to try to convince the terminal not to detect that it's been written to in some particular situation. > Some emulators have "scroll to bottom on tty input" as well as (or > instead of) "on tty output" -- if possible with your emulator, you > could try enabling only the former. Sure.  There's little practical difficulty, I'm mostly interested in the theory of the thing.  Thanks Bart. >