From: rob@plan9.att.com rob@plan9.att.com
Subject: Acme gags, if pushed too far!!!
Date: Tue, 15 Aug 1995 11:55:01 -0400 [thread overview]
Message-ID: <19950815155501.05RVgrcXfZKt2UpEM7M59uxngxBwPYWQur3DO-Ds3ZQ@z> (raw)
This is a silly bug with no easy guaranteed fix. The code has a check
against the problem but it's too lax. Change the appearances of the
value 20 in /sys/src/cmd/acme/rows.l to 80 and that should cover
most cases. A proper fix involves rewriting the underlying frame library,
which may happen someday but not anytime soon. I have placed the
diffs in the errata web page. It's not worth posting a new binary; just
avoid making columns so uselessly narrow.
-rob
next reply other threads:[~1995-08-15 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-15 15:55 rob [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-15 8:02 Fariborz
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=19950815155501.05RVgrcXfZKt2UpEM7M59uxngxBwPYWQur3DO-Ds3ZQ@z \
--to=rob@plan9.att.com \
/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).