From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] ghostscript not finding LucidaSans
Date: Sun, 27 Jun 2010 21:07:14 -0400 [thread overview]
Message-ID: <731ED516-1A13-4296-BE0C-2C18D7D62532@mac.com> (raw)
From an install to 9vx (built from mercurial on OS X 10.5.8) from
yesterday's CD image (though apparently some people on IRC have this
problem too):
term% man -P man
converting from troff to postscript...
reading through postscript...
Ghostscript Error:
postnote 307: sys: write on closed pipe pc=0x0001f8fc
Fontmap entry for LucidaSans ends prematurely! Giving up.
converting from troff to postscript...
reading through postscript...
Ghostscript Error:
postnote 358: sys: write on closed pipe pc=0x0001f8fc
Fontmap entry for LucidaSans ends prematurely! Giving up.
term% troff | page # let's try without referencing LucidaSans at all
Hello
(^d)\x04converting from troff to postscript...
reading through postscript...
Ghostscript Error:
postnote 404: sys: write on closed pipe pc=0x0001f8fc
Fontmap entry for LucidaSans ends prematurely! Giving up.
I don't understand what's going on here but as far as I can tell /sys/
lib/postscript/fonts/LucidaSans has never existed in the Plan 9
directory tree (checking sourcesdump) and my old VM works fine without
it. Anyone know what's going on here? Thanks.
next reply other threads:[~2010-06-28 1:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 1:07 Pietro Gagliardi [this message]
2010-06-28 1:56 ` erik quanstrom
2010-06-28 3:18 ` Pietro Gagliardi
2010-06-28 4:40 ` erik quanstrom
2010-06-28 6:24 ` Pietro Gagliardi
2010-06-28 6:36 ` Pietro Gagliardi
2010-06-28 13:09 ` erik quanstrom
2010-06-28 14:23 ` Pietro Gagliardi
2010-06-28 15:04 ` ron minnich
2010-06-28 18:05 ` [9fans] problems with tracing 9vx on os x (was: " Pietro Gagliardi
2010-06-29 8:03 ` yy
2010-06-29 14:31 ` Pietro Gagliardi
2010-06-28 12:21 ` [9fans] " Ethan Grammatikidis
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=731ED516-1A13-4296-BE0C-2C18D7D62532@mac.com \
--to=pietro10@mac.com \
--cc=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).