From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] how people learn things (was architectures)
Date: Fri, 13 Jul 2001 15:38:48 +0200 [thread overview]
Message-ID: <0a0e01c10ba1$256ac900$c0b7c6d4@SOMA> (raw)
In-Reply-To: <20010713124934.B1573199E4@mail.cse.psu.edu>
> while(`{read}){
> troff ... |lp -dstdout > x.ps
> page x.ps
> }
i've fought a lot with �sloth's 'wysiwyg' -- it isn't.
i find myself in exactly the same loop. i think wordpad
is the _worst_ because from what you saw and printed
a week ago is no longer the same a week later.
given i had all these envelopes with postcode boxes and
i had an OCR font i thought i'd make a generic template
with wordpad and then have a bunch of files with one
address per file and then print them directly on the
envelopes.
to get the generic templates took _hours of pure
hackery_. later, every time i printed an address
it was always not where it had been.
at least with troff i can say go to (x, y) and put down
some chunk of text. yes, i will have to loop a bit, to
get the generic, but it _will_ work the next time.
they have a copy of the code to word 2 at la cit� des
sciences et de la technologie (i think that's it). when
i saw it i thought 'bound to be a chunk of os/360', but
no, a metre high stack of paper -- 600k lines of code.
and _that_ was word 2!
i wrote some code to print stuff on '95. really simple
(or so you'd think) 4 or 5 columns of text on an A4 page.
impossible, absolutely impossible, without writing a
huge chunk of code. i cheated.
next prev parent reply other threads:[~2001-07-13 13:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 12:49 presotto
2001-07-13 13:38 ` Boyd Roberts [this message]
2001-07-13 15:44 ` Douglas A. Gwyn
2001-07-14 0:19 ` Boyd Roberts
2001-08-02 10:27 ` Ralph
2001-08-02 11:24 ` Boyd Roberts
2001-08-03 9:05 ` Ralph Corderoy
2001-08-03 10:15 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 18:15 David Gordon Hogan
2001-07-16 16:21 rog
2001-07-16 16:46 ` suspect
2001-07-13 16:32 jmk
2001-07-16 8:55 ` Douglas A. Gwyn
2001-07-16 15:21 ` Rick Hohensee
2001-07-13 16:22 rog
2001-07-14 0:23 ` Boyd Roberts
2001-07-16 8:54 ` Douglas A. Gwyn
2001-07-16 15:46 ` david presotto
2001-07-13 9:17 okamoto
2001-07-13 9:12 okamoto
2001-07-13 10:07 ` Boyd Roberts
2001-07-13 10:49 ` Lucio De Re
2001-07-13 10:59 ` Boyd Roberts
2001-07-13 11:11 ` Lucio De Re
2001-07-13 15:26 ` Douglas A. Gwyn
2001-07-13 16:20 ` Lucio De Re
2001-07-14 0:28 ` Boyd Roberts
2001-07-16 8:54 ` Douglas A. Gwyn
2001-07-16 9:55 ` Boyd Roberts
2001-07-13 8:00 Laura Creighton
2001-07-13 9:48 ` Boyd Roberts
2001-07-13 15:25 ` Douglas A. Gwyn
2001-07-13 15:44 ` Boyd Roberts
2001-07-13 20:47 ` Steve Kilbane
2001-07-14 14:45 ` Boyd Roberts
2001-07-13 15:25 ` Douglas A. Gwyn
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='0a0e01c10ba1$256ac900$c0b7c6d4@SOMA' \
--to=boyd@fr.inter.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).