zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: ticking clock
Date: Tue, 14 Aug 2018 12:07:31 +0200	[thread overview]
Message-ID: <CAKc7PVCzNheVHh84ndA9MF=FODFr5O10bqBvZTS0C+tAJ0f05w@mail.gmail.com> (raw)
In-Reply-To: <5d1d108b-d65d-9c5b-64fa-017d3a9637a8@eastlink.ca>

On Mon, 13 Aug 2018 at 18:09, Ray Andrews <rayandrews@eastlink.ca> wrote:
> I did this in zshrc:
>
>      ## 2018-08-10: ticking clock:
>      #RPS1=$'%t %w'
>      RPS1='%B%F{yellow}[%D{%L:%M:%S}]%f %w'
>      TMOUT=1
>      TRAPALRM() { zle reset-prompt }
>
> Nice to have the time ticking away there, but it kills back-scrolling --
> I scroll up, but every tick moves back to the bottom.  Fixable?

Maybe the terminal emulator has configuration option to not scroll
down on view-update? Turning it on is useful in general, allows to
e.g. scroll up and read ./configure log while it's still processing.

-- 
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin


      parent reply	other threads:[~2018-08-14 10:07 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
2018-08-14 10:07       ` Sebastian Gniazdowski [this message]

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='CAKc7PVCzNheVHh84ndA9MF=FODFr5O10bqBvZTS0C+tAJ0f05w@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=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).