From: Scott Schwartz schwartz@bio.cse.psu.edu
Subject: [9fans] Re: 9libs, new sam release, experimental wily release
Date: Mon, 14 Jun 1999 02:44:31 -0400 [thread overview]
Message-ID: <19990614064431.07xepPbhC18MCUY7264LcmTkwlK_0Uz6CHeChbFXRmc@z> (raw)
"Mark H. Wilkinson" <mhw@kremvax.demon.co.uk> writes:
| 9libs-1.0, sam-9libs, wily-9libs
Thanks. I have a couple of complaints, though. Several of my
favorite bugs (patches posted ages ago) have been resurrected
in this new release.
They are:
* In samterm, MAXFILES is too small. (I've been using 4K.)
* In sam, private temp files are world readable/writable.
* In libXg, "fontfile" is specified by the X client app. In general
that cannot work: unlike in Plan 9, the X terminal usually won't
share any filesystem with the machine on which the X app is
running, so *no* filename can be valid for "-p9font". The fix is
to store the unicode font map in an X property which is set by your
xinitrc.
I'll dig the diffs out of my RCS files tomorrow and sent them along.
reply other threads:[~1999-06-14 6:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19990614064431.07xepPbhC18MCUY7264LcmTkwlK_0Uz6CHeChbFXRmc@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).