From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: "Mark H. Wilkinson" <mhw@kremvax.demon.co.uk>
Cc: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>,
Bengt Kleberg <bengt@softwell.se>
Subject: Re: 9libs, new sam release, experimental wily release
Date: Mon, 14 Jun 1999 20:10:04 -0400 [thread overview]
Date: Mon, 14 Jun 1999 20:10:04 -0400 [thread overview]
Message-ID: <19990615001004.7754.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Your message of "Mon, 14 Jun 1999 20:46:50 BST." <199906142046.20514.9libs.badum@kremvax.demon.co.uk>
"Mark H. Wilkinson" <mhw@kremvax.demon.co.uk> writes:
| > * 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.
|
| By this, do you mean the case where you're logging into remote machines
| and running sam & samterm on the remote machine?
Yes.
| ... but I guess you're after a
| solution which is easier to manage, using the X server as shared storage.
Yup.
| That sounds reasonable, but I'd like to retain the existing mechanism
| too: it works well in networks where the file system is common to all
| machines to some degree.
Of course. The patch does that. It checks to see if the fontfile
starts with '.' or '/', and if so, reads that file. Otherwise it
treats it as the literal contents of the font file. In either case, as
before, it falls back to using a literal X font name if the previous
steps don't resolve to a font file.
| That would be great!
I'll have them ready soon. I got diverted hacking on 9term today.
next prev parent reply other threads:[~1999-06-15 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-10 23:04 Mark H. Wilkinson
1999-06-14 6:44 ` Scott Schwartz
1999-06-14 19:46 ` Mark H. Wilkinson
1999-06-15 0:10 ` Scott Schwartz [this message]
1999-06-15 0:39 ` Scott Schwartz
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=19990615001004.7754.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--cc=bengt@softwell.se \
--cc=mhw@kremvax.demon.co.uk \
--cc=sam-fans@hawkwind.utcs.toronto.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).