From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] PIC language
Date: Thu, 20 Nov 2003 19:37:36 +0100 [thread overview]
Message-ID: <04aa01c3af95$5efe0700$b9844051@insultant.net> (raw)
In-Reply-To: <ACCF003CBA3D09458207DB0CB86AD17D124C34@XMAIL.asuch.cas.cz>
> still thinking of pic as an output format for another program i'm going to
write ...
there was a thing called cip(1) which was a blit program so you could 'draw'
what you wanted and it wrote pic. iirc, it was more of an experiment than
a production tool.
next prev parent reply other threads:[~2003-11-20 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 15:48 cej
2003-11-20 16:50 ` Russ Cox
2003-11-20 18:37 ` boyd, rounin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-18 14:46 cej
2003-11-19 9:41 ` Douglas A. Gwyn
2003-11-19 17:05 ` boyd, rounin
2003-11-19 17:10 ` Fco.J.Ballesteros
2003-11-19 18:01 ` John Stalker
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='04aa01c3af95$5efe0700$b9844051@insultant.net' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.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).