From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re[3]: Link
Date: Wed, 05 Sep 2001 09:12:10 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010905091055.02436f50@server-1> (raw)
In-Reply-To: <7423814302.20010904224713@bigfoot.com>
At 10:47 PM 9/4/2001 +0200, Giuseppe Bilotta wrote:
>Perfect, thanks. Now how is the 3rd used? (That is, why is it on a
>separate part?)
because it depends on the special driver how it is used/embedded as well as
that #'s are nasty things in tex; it's also more clear
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
prev parent reply other threads:[~2001-09-05 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-02 23:38 Link David Arnold
2001-09-04 7:18 ` Link Jens Scheidtmann
2001-09-04 9:43 ` Link Hans Hagen
2001-09-04 12:32 ` Re[2]: Link Giuseppe Bilotta
2001-09-04 16:08 ` Hans Hagen
2001-09-04 20:47 ` Re[3]: Link Giuseppe Bilotta
2001-09-05 7:12 ` Hans Hagen [this message]
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=5.1.0.14.1.20010905091055.02436f50@server-1 \
--to=pragma@wxs.nl \
--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).