From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pic generators?
Date: Wed, 5 Feb 2003 16:15:45 +0100 [thread overview]
Message-ID: <4c8ab11b60b74578a8bf78bb19123512@plan9.escet.urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.30.0302051010000.17267-100000@athena>
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
I wrote pic by hand a few months ago for the very first time.
It's not hard to learn.
http://plan9.escet.urjc.es/sys/doc/pic.ps
was a great help.
hth
[-- Attachment #2: Type: message/rfc822, Size: 1679 bytes --]
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] pic generators?
Date: Wed, 5 Feb 2003 10:11:57 -0500 (EST)
Message-ID: <Pine.LNX.4.30.0302051010000.17267-100000@athena>
...
So the figures in, say, the il paper were written by hand?
I don't mind learning pic if it was designed to be human
writable. I just need to be told that.
:)
On Wed, 5 Feb 2003, Fco.J.Ballesteros wrote:
> xfig (linux and others) generates pic, if you don't want
> to write pic yourself.
>
next prev parent reply other threads:[~2003-02-05 15:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 14:59 Sam
2003-02-05 15:05 ` Fco.J.Ballesteros
2003-02-05 15:11 ` Sam
2003-02-05 15:15 ` Fco.J.Ballesteros [this message]
2003-02-05 15:54 ` Boyd Roberts
2003-02-05 17:01 ` Charles Forsyth
2003-02-05 15:59 ` Russ Cox
2003-02-05 20:23 ` William Josephson
2003-02-06 9:40 ` Douglas A. Gwyn
2003-02-05 15:38 ` David Butler
2003-02-05 16:31 ` Jon Snader
2003-02-06 12:52 ` Aharon Robbins
2003-02-07 12:33 ` Ralph Corderoy
2003-02-07 14:28 ` [9fans] troff book (was: pic generators?) Sam
2003-02-10 10:04 ` Ralph Corderoy
2003-02-05 17:05 ` [9fans] pic generators? Skip Tavakkolian
2003-02-05 16:36 rog
2003-02-05 16:36 ` Russ Cox
2003-02-06 0:46 okamoto
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=4c8ab11b60b74578a8bf78bb19123512@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).