From: Andrew McVeigh andrew@abc.gov.au
Subject: Memory problems with 8-1/2
Date: Sun, 24 Sep 1995 19:42:03 -0400 [thread overview]
Message-ID: <19950924234203.jkuixIpKPiCZNhVw5wA97l1chB_wtrFPAPNQNJxb4gs@z> (raw)
Hi all,
I have managed to install Plan-9 and get 8-1/2 working @1024x768x8.
I really love the acme editor/environment and the excellent alef
language.
Anyway, I seem to only be able to open about 3 large windows...
If I have only one window on the screen then I can move it and
reshape it etc, but with three windows (depends on the size of each)
on the screen then all windowing operations seem to fail. I seem
to remember seeing a message at one stage saying something like
"Out of Bitmap Memory"... Is this the case or is something else
wrong? Is there a fixed amount of memory allocated to windows?
Thanks for any help in advance,
Andrew McVeigh
p.s. replies by e-mail preferred, as my news feed is absurdly slow.
next reply other threads:[~1995-09-24 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-24 23:42 Andrew [this message]
1995-09-25 14:16 presotto
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=19950924234203.jkuixIpKPiCZNhVw5wA97l1chB_wtrFPAPNQNJxb4gs@z \
--to=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).