From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pic
Date: Wed, 15 Oct 2003 00:31:28 -0700 [thread overview]
Message-ID: <536b6900e83f1fda1560da148dde883f@centurytel.net> (raw)
In-Reply-To: <6c4f793e579880af13afdb87573b71ce@caldo.demon.co.uk>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
>>>Also there doesn't seem to be any
>>>target for tpic.
>
> cd /sys/src/cmd/tex/tpic; mk install
>
> what was the problem with pic?
Thanks; Russ also hinted at that.
I was mostly fighting myself. It's been a while since I pic'ed. I did
have a couple of suicides with tpic on some bad input. I didn't investigate,
but I can try to investigate it when I have some time.
The man page for pic includes two identical examples; I'm not smart
enough to know if that is on purpose ☺
FYI, I was building a pic that shows the steady-state process/data flow
in srvold9p. I've attached in case somebody is interested.
[-- Attachment #2.1: Type: text/plain, Size: 312 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Disposition: attachment; filename=srvold9p.pic
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
[-- Attachment #2.2: srvold9p.pic.suspect --]
[-- Type: application/octet-stream, Size: 809 bytes --]
.PS
S: [
circle "srvold9p" "[serve]" dotted
move
A: circle "srvold9p" "[serve]"
move
circle "srvold9p" "[serve]" dotted
]
box ht 0.5*boxht wid S.wid with .s at S.n+0,0.5 "/mnt/term" dashed
line from last box.s to S.A.n <-> "9P2000"
R: [
boxht=boxht*.5
box "rendez tag 0" dotted
move
B: box "rendez tag 1"
move
box "rendez tag n" dotted
] with .n at S.s+0,-0.5
arrow from R.B.n to S.A.s
X: [
D: circle "srvold9p" "[demux]"
arrow <-
F: circle "srvold9p" "[fcall]"
] with .nw at R.se+0.5,-0.5
spline from X.D.w left 2 then up to R.B.s ->
Y: [
G: circle "drawterm"
] with .sw at X.ne+0.5,0.5
spline from S.A.ne right up then right 3 then down 1.25 then right to Y.G.nw ->
spline from Y.G.sw left 0.25 then down 0.75 to X.F.e ->
"9P1" at Y.G.w-0.25,0.0
.PE
next prev parent reply other threads:[~2003-10-15 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 19:48 Skip Tavakkolian
2003-10-13 20:12 ` Russ Cox
2003-10-15 5:51 ` Charles Forsyth
2003-10-15 7:31 ` Skip Tavakkolian [this message]
2003-10-16 22:03 ` Charles Forsyth
2011-05-23 22:56 Steve Simon
2011-05-23 23:05 ` Skip Tavakkolian
2011-05-23 23:19 ` Venkatesh Srinivas
2011-05-24 1:19 ` Iruatã Souza
2011-05-24 2:26 ` Anthony Sorace
2011-05-24 16:11 ` Anthony Sorace
2011-05-24 2:53 ` Russ Cox
2011-05-24 15:32 ` roger peppe
2011-05-24 15:48 ` simon softnet
2011-05-24 16:22 ` Russ Cox
2011-05-24 5:03 ` tlaronde
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=536b6900e83f1fda1560da148dde883f@centurytel.net \
--to=fst@centurytel.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).