zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: ticking clock
Date: Tue, 14 Aug 2018 14:21:15 -0700	[thread overview]
Message-ID: <5c13aae7-ddd8-8f2f-a818-f38dba14150f@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7aAP0Ko+K1fzH7m_4nADXbXJoMeyMaODzah32Q=OhqcDw@mail.gmail.com>

On 14/08/18 10:27 AM, Bart Schaefer wrote:
> On Mon, Aug 13, 2018 at 3:45 PM, Ray Andrews <rayandrews@eastlink.ca> 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.


>


  reply	other threads:[~2018-08-14 21:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 13:49 separating functions, fpath, and autoload TJ Luoma
2018-08-13 13:55 ` TJ Luoma
2018-08-13 13:56 ` Pier Paolo Grassi
2018-08-13 14:31   ` Daniel Shahaf
2018-08-13 15:38     ` ticking clock Ray Andrews
2018-08-13 16:29       ` Vin Shelton
2018-08-13 19:57         ` Ray Andrews
2018-08-13 21:54           ` Bart Schaefer
2018-08-13 22:45             ` Ray Andrews
2018-08-14 17:27               ` Bart Schaefer
2018-08-14 21:21                 ` Ray Andrews [this message]
2018-08-14 10:07       ` Sebastian Gniazdowski

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=5c13aae7-ddd8-8f2f-a818-f38dba14150f@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).