From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Lex, Yacc, Unicode Plane 1
Date: Fri, 29 Jan 2010 01:08:25 -0500 [thread overview]
Message-ID: <2179391c5e79f180197d72711e5fe00a@ladd.quanstro.net> (raw)
In-Reply-To: <dd6fe68a1001281636g6f44596x879fd7f80e102270@mail.gmail.com>
if you're doing this in plan 9, bootstrapping the compiler
is a bit of a pain. this could save some hassle:
/n/sources/contrib/quanstro/8c-32bitrune
these are the patches it turns out were missing
/n/sources/patch/cc-32bitrune
/n/sources/patch/sed-32bitrune
/n/sources/patch/ed-32bitrune
/n/sources/patch/libdraw-32bitrune
/n/sources/patch/sambufsz
there doesn't appear to be a convention for entering 32-bit runes
in p9p yet, as in compose + X + hhhh. i propose by silly extension
compose + Y + hhhhhh.
i've got my system working to the point where i can type
compose + Y01d510 with the clarisr font and get a
fraktur m on the screen. nothing like a useless demo.
one thing i really love about plan 9 is the ability to make
big changes like this without having as step 1: boil the
oceans.
- erik
next prev parent reply other threads:[~2010-01-29 6:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 19:43 Karljurgen Feuerherm
2010-01-28 20:05 ` erik quanstrom
2010-01-28 20:46 ` geoff
2010-01-28 20:59 ` Karljurgen Feuerherm
2010-01-28 21:20 ` geoff
2010-01-28 21:51 ` Karljurgen Feuerherm
2010-01-28 22:07 ` ron minnich
2010-01-28 22:19 ` hiro
2010-01-28 22:34 ` Karljurgen Feuerherm
2010-01-28 22:56 ` erik quanstrom
2010-01-28 23:38 ` Federico G. Benavento
2010-01-28 23:42 ` erik quanstrom
2010-01-29 0:08 ` Karljurgen Feuerherm
2010-01-29 0:19 ` Rob Pike
2010-01-29 0:24 ` erik quanstrom
2010-01-29 0:36 ` Russ Cox
2010-01-29 0:42 ` erik quanstrom
2010-01-29 0:58 ` Russ Cox
2010-01-29 6:08 ` erik quanstrom [this message]
2010-01-29 6:18 ` Justin Jackson
2010-01-29 14:36 ` 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=2179391c5e79f180197d72711e5fe00a@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).