zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Cc: Patrick Oscity <patrick.oscity@gmail.com>
Subject: Re: Bug report
Date: Sat, 14 Dec 2013 11:08:30 -0800	[thread overview]
Message-ID: <131214110830.ZM18442@torch.brasslantern.com> (raw)
In-Reply-To: <9CB4226B-47EE-44FA-8F8F-01DF4CB5154D@gmail.com>

On Dec 14,  7:44pm, Patrick Oscity wrote:
}
} 	* the right prompt is not right aligned, it is in fact shifted to the
} 	  left by one character

This is intentional, because a particular kind of terminal device that
was very widespread a few years ago had a misfeature wherein printing to
the lower right corner character position scrolls the screen up a line.

Terminal types that have this behavior are not readily identifiable from
terminfo descriptions, and the extra space along the right side was
deemed less annoying than an entire extra line across the bottom (and
corresponding loss of whatever was in the line that scrolled off the
top).

Worse, there was another common terminal where filling the bottom line
of the screen and then writing a trailing newline would NOT scroll the
display, resulting in e.g. blank lines disappearing from output.

Much easier than attempting to detect different combinations of this was
to always be sure that the only thing ever written in the lower right
corner *is* a newline, and only when scrolling is wanted.

Given the number of other prompt-specific setopts we have at this point,
we could potentially add another one to control this, but I think the
default behavior should remain as it is.


  reply	other threads:[~2013-12-14 19:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14 18:44 Patrick Oscity
2013-12-14 19:08 ` Bart Schaefer [this message]
2013-12-14 20:43   ` Peter Stephenson
2013-12-15  1:15     ` Bart Schaefer
2013-12-15 13:30       ` Peter Stephenson
2013-12-15 17:10         ` Bart Schaefer
2013-12-15  1:08   ` Patrick Oscity
2013-12-15 11:01   ` Patrick Oscity
  -- strict thread matches above, loose matches on Subject: below --
2021-03-01  9:43 BUG REPORT ZheNing Hu
2021-03-01 15:27 ` Daniel Shahaf
2021-03-01 17:32 ` Bart Schaefer
2021-03-05  7:51   ` ZheNing Hu
2019-09-19 11:16 Bug report Vladimir Deyter
2019-09-19 14:53 ` Mikael Magnusson
2019-09-19 15:57   ` Daniel Shahaf
2014-12-26 16:53 mvxxc
2014-12-27  2:35 ` Bart Schaefer
2014-09-17  0:26 bug report Mica Chimera
2014-09-17  1:08 ` Frank Terbeck
2014-06-05 17:05 robin terrep-drangiug
2014-06-05 20:48 ` Bart Schaefer
2013-12-17 10:59 Bug report Patrick Oscity
2013-12-17 11:27 ` Peter Stephenson
2013-12-17 17:11 ` Bart Schaefer
2013-12-17 17:56   ` Bart Schaefer
2013-08-04 12:16 Bug Report Yuusuke Yoshimoto
2013-08-04 17:58 ` Peter Stephenson
1996-05-22  0:07 Bug report Felix von Leitner
1996-05-15  7:48 Martin Birgmeier
1996-05-10  8:30 Martin Birgmeier
1995-08-24 11:23 Bug Report Carsten Friedrich

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=131214110830.ZM18442@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=patrick.oscity@gmail.com \
    --cc=zsh-workers@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).