From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 C compiler for RISC-V by Richard Miller
Date: Tue, 30 Oct 2018 06:52:37 +0200 [thread overview]
Message-ID: <CAJQ9t7jJ1YLdDjsFZRav=TeT4VhpZ1U52h4L6p5WU7f-c6ySrw@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5hjvh1J1ZdQfAzdi5KLHY8DXK_z=8Anz44X7fXGE8Yucw@mail.gmail.com>
On 10/29/18, Charles Forsyth <charles.forsyth@gmail.com> wrote:
> It's z because the Atmel AVR is the last thing you'd want to use. (As
> usual, once you've got C going, it's ok, except for the design bugs.)
Sadly, some of the Atmel kit I'd like to play with is no longer
supported, the CPUs are nowhere to be sourced from in reasonable
quantities. So that's yet another nail in that coffin.
> I had a chart somewhere with the available non-unicode letters.
>
Is there a technical reason (beside fonts that do not cover them) not
to use a Unicode values for the first letter? We could perhaps grab a
bunch of unassigned codes and design glyphs for them? Use them as
logos?
Lucio.
next prev parent reply other threads:[~2018-10-30 4:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 7:24 Skip Tavakkolian
2018-10-27 18:24 ` Sean Hinchee
2018-10-27 18:45 ` hiro
2018-10-28 11:38 ` Richard Miller
2018-10-28 19:23 ` hiro
2018-10-30 17:03 ` Richard Miller
2018-10-28 11:32 ` Richard Miller
2018-10-28 12:41 ` arnold
2018-10-28 13:55 ` Skip Tavakkolian
2018-10-28 15:28 ` Charles Forsyth
2018-10-28 18:48 ` David du Colombier
2018-10-28 19:03 ` Steve Simon
2018-10-29 13:02 ` Lucio De Re
2018-10-29 14:07 ` Richard Miller
2018-10-29 16:13 ` Lucio De Re
2018-10-29 16:26 ` Charles Forsyth
2018-10-30 4:52 ` Lucio De Re [this message]
2018-10-30 12:41 ` Ethan Gardener
2018-10-30 14:55 ` Steve Simon
2018-10-30 15:16 ` Charles Forsyth
2018-10-30 15:37 ` Steve Simon
2018-10-31 13:42 ` Ethan Gardener
2018-10-31 17:04 ` Charles Forsyth
2018-10-30 9:32 ` Anthony Martin
2018-10-30 10:31 ` Richard Miller
2018-10-31 5:18 ` Anthony Martin
2018-10-31 9:36 ` Richard Miller
2018-10-30 15:06 ` Charles Forsyth
[not found] <857020832.6276700.1540912554946.ref@mail.yahoo.com>
2018-10-30 15:15 ` Brian L. Stuart
2018-10-31 13:48 ` Ethan Gardener
2018-11-10 1:04 ` Lyndon Nerenberg
2018-11-10 3:28 ` erik quanstrom
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='CAJQ9t7jJ1YLdDjsFZRav=TeT4VhpZ1U52h4L6p5WU7f-c6ySrw@mail.gmail.com' \
--to=lucio.dere@gmail.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).