From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Re: test suite in the garden
Date: Wed, 27 Jul 2005 09:33:33 +0200 [thread overview]
Message-ID: <42E738CD.8030108@elvenkind.com> (raw)
In-Reply-To: <m2y87t9rmh.fsf@levana.de>
Patrick Gundlach wrote:
>
> Don't call me magic. I am currently trying to understand the tftopl,
> pltotf, vftovp and vptovf programs in detail. And I am so miserable at
> that; all kinds of optimizations that makes the code unreadable.
I've spent the better part of the last week trying to come to terms
with the eq_define() and unsave() routines in TeX, so I can relate
to that :-/
Taco
next prev parent reply other threads:[~2005-07-27 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 18:52 Strange behaviour of \bTABLE ... \eTABLE Elena Fraboschi
2005-07-25 20:04 ` Mojca Miklavec
2005-07-25 20:42 ` test suite in the garden (was: Strange behaviour of \bTABLE) Henning Hraban Ramm
2005-07-25 22:12 ` test suite in the garden Hans Hagen
2005-07-26 21:36 ` Patrick Gundlach
2005-07-26 22:23 ` Mojca Miklavec
2005-07-26 22:38 ` Patrick Gundlach
2005-07-27 7:33 ` Taco Hoekwater [this message]
2005-07-25 20:46 ` Strange behaviour of \bTABLE ... \eTABLE Hans Hagen
2005-07-26 8:22 ` Taco Hoekwater
2005-07-25 20:43 ` Hans Hagen
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=42E738CD.8030108@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
/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).