zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: ZSH vertical resize - last terminal line disappears
Date: Sun, 14 Feb 2016 10:31:43 -0800	[thread overview]
Message-ID: <160214103143.ZM20574@torch.brasslantern.com> (raw)
In-Reply-To: <CACBfHbx9qaJjqNne70P1KM_u_i7yOeoxpK_7-OM+_kq49GvkqA@mail.gmail.com>
In-Reply-To: <CACBfHbxkda132j8RCXRz+dcU0St+uan1-H5RkxgFUtFL1pXA3w@mail.gmail.com>

On Feb 9,  8:13pm, Florian Meier wrote:
} 
} Every time I split my terminal vertically (or just resize it), the
} last line of the text output disappears or just gets overwritten by
} the prompt, I don't know.


On Feb 10,  4:40pm, Florian Meier wrote:
}
} As a follow-up, i found a workaround by accident.
} When the first line (the "-----------" line) does not reach the column
} on the very right, the problem disappears...
} Is someone able to reproduce this weird behavior?


So what's happening is that the terminal *might* scroll when a character
is printed in the bottom right corner.  This behavior depends on the
terminal type and sometimes on a configurable setting for the terminal.
Sometimes it depends on whether that last character is a space or a
newline or is followed by a newline.  There's some discussion of this
in the manual under the ZLE_RPROMPT_INDENT variable.

Depending on whether this happens or not, ZLE can get confused about
the number of lines it needs to move upward from the bottom of the
screen in order to redraw the prompt.

The difficulty is that there's no reliable way to determine how any
given terminal will behave; even when there is a corresponding terminfo
field, it is often incorrect.  No matter what we do it'll always be
wrong for somebody.  Your workaround -- avoiding lines that print all
the way to the right margin is the only 100% effective approach.


  reply	other threads:[~2016-02-14 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 19:13 Florian Meier
2016-02-10 15:40 ` Florian Meier
2016-02-14 18:31   ` Bart Schaefer [this message]
2016-05-04 17:32 ` Sebastian Gniazdowski
2016-05-05  1:33   ` Bart Schaefer

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=160214103143.ZM20574@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).