zsh-workers
 help / color / mirror / code / Atom feed
From: Geoff Wing <mason@werple.net.au>
To: zsh-workers@math.gatech.edu (zsh-list)
Cc: A.Main@dcs.warwick.ac.uk
Subject: Re: ZLE scrolly bugfix
Date: Thu, 18 Jul 1996 04:38:38 +1000 (EST)	[thread overview]
Message-ID: <199607171838.SAA00748@werple.net.au> (raw)
In-Reply-To: <7795.199607171117@stone.dcs.warwick.ac.uk>

Zefram wrote:
:If the cursor gets onto the last line of the screen and there's
:more text off the bottom of the screen, it's possible to have the
:cursor over the <.... marker when it's really in the text hidden
:under that.  Also, the cursor doesn't go onto the last position on
:the screen properly on a terminal that moves the cursor onto the
:next line as soon as something is written to the last column.
:I fix both of these problems by having refresh() avoid putting
:the cursor on the last line if possible.  If there's no more text,
:obviously, it can't avoid putting the cursor there, but then it's
:not a problem.

Yep, these are bugs.  However the patch doesn't fix these properly.
In  nextline, if  nvln == winh - 1 (or --ln as you put it), then 
you would still need to scroll one line and adjust nvln.
I'll look at this (after I get some sleep).
I was thinking about breaking up scrollwindow() into scroll a single
line and scroll a half screen.

And for Zoltan and others who want to use zed to edit their stuff
and want half window scrolls, chuck "local BAUD=2400" at the top
somewhere.  Other refresh styles will have to wait till after zsh 3.0
-- 
Mason [G.C.W]  mason@werple.mira.net.au    "Hurt...Agony...Pain...LOVE-IT"



  reply	other threads:[~1996-07-17 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-17 11:17 Zefram
1996-07-17 18:38 ` Geoff Wing [this message]
1996-07-17 18:56   ` Zefram
1996-07-18  9:20     ` Geoff Wing

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=199607171838.SAA00748@werple.net.au \
    --to=mason@werple.net.au \
    --cc=A.Main@dcs.warwick.ac.uk \
    --cc=zsh-workers@math.gatech.edu \
    /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).