From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] acme "safe"
Date: Mon, 24 Jul 2006 09:22:54 -0700 [thread overview]
Message-ID: <ee9e417a0607240922p16c42af2u896b812f0f1ae1ce@mail.gmail.com> (raw)
In-Reply-To: <c4848865081cfb203b5aedd619d7a788@vitanuova.com>
> does anyone know what "safe" implies in the context of the acme source code?
> e.g. in
> winresize(Window *w, Rectangle r, int safe, int keepextra)
I believe that safe means the associated data structure elements
or screen bits are all up-to-date. So if safe is false, winresize needs
to redraw the entire window. But if safe is true, winresize can assume
the window as currently described by the Window *w is correctly drawn,
and need only redraw what it changes.
Russ
prev parent reply other threads:[~2006-07-24 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 14:28 rog
2006-07-24 16:22 ` Russ Cox [this message]
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=ee9e417a0607240922p16c42af2u896b812f0f1ae1ce@mail.gmail.com \
--to=rsc@swtch.com \
--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).