9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] invisible prompt in win
Date: Sat, 18 Oct 2008 10:18:28 -0700	[thread overview]
Message-ID: <dd6fe68a0810181018m3bb1f397x73e5648766b5935b@mail.gmail.com> (raw)
In-Reply-To: <1c2f6d7c0810022314l5f79f801mc9a59077a7cb1b@mail.gmail.com>

This is not a bug.

At any point in time, there is a character position
associated with the upper left corner of the text window.
Text before that position is not shown; text at or after
that position is shown, until it runs off the bottom of
the window.  Let's call that upper left character position p0.

Most of the time, acme/sam/rio work to arrange that p0
follows a newline character, so that the window begins
at the beginning of a line.  Sometimes this is not possible.
One case is when a line is very long--longer than the
entire window--and you want to see the end of it.
Another case is when you tell acme/sam/rio to scroll past
the end of the text.  Then p0 is the end of the text,
right where your cursor is.  When you type new text,
it correctly shows at p0.  The prompt is still there, just
off the window to the top.

You are expecting line-oriented behavior in a "stream of bytes" world.

Russ


  parent reply	other threads:[~2008-10-18 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03  6:14 Michael Brown
2008-10-03  8:27 ` Robert Raschke
2008-10-18 17:18 ` Russ Cox [this message]
2008-10-03 12:19 erik quanstrom
     [not found] <4140ffe20ee64117b535a4311e7dced9@quanstro.net>
2008-10-03 13:11 ` Robert Raschke
2008-10-03 13:28 erik quanstrom
     [not found] <c0b32b43ea34dbdeab36f74bab861b88@quanstro.net>
2008-10-03 13:53 ` Robert Raschke
2008-10-03 17:50 erik quanstrom
2008-10-04 19:58 ` Martin Neubauer
2008-10-05 13:52   ` erik quanstrom
2008-10-05 15:07     ` Pietro Gagliardi
2008-10-05 15:22 erik quanstrom

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=dd6fe68a0810181018m3bb1f397x73e5648766b5935b@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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.
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).