From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] bug in rio
Date: Tue, 24 Oct 2000 23:40:16 -0700 [thread overview]
Message-ID: <200010250640.e9P6eGG56159@ducky.net> (raw)
to reproduce:
1. create a window and enable automatic scrolling on the button 2 menu.
call this Window 1.
start a process in that window that will continuously print output, e.g.:
while (~ x x) {
echo hi
sleep 1
}
2. move another window (call it Window 2) slowly across the front of
the scrolling window. the borders of Window 2 will be "captured" by
the block copies due to the scrolling in Window 1. you will see
garbage copies of the border slowly scroll off the top of Window 1.
i don't know any way to make the garbage go away except by hiding
and then unhiding Window 1. unlike other window systems i have used,
rio does not seem to have a "refresh" command. i imagine this is because
reliable backing store ought to make that unnecessary. alas...
(N.B. the lack of a refresh command is also annoying in the case
that kernel messages pollute your display; i occasionally get stray
interrupt messages that seem to somehow be associated with the Tekram
scsi controller.)
next reply other threads:[~2000-10-25 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 6:40 Mike Haertel [this message]
2000-10-25 14:26 ` rob pike
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=200010250640.e9P6eGG56159@ducky.net \
--to=mike@ducky.net \
--cc=9fans@cse.psu.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.
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).