From: "Denis B. Roegel" <Denis.Roegel@loria.fr>
Cc: Denis.Roegel@loria.fr (Denis B. Roegel),
ntg-context@ntg.nl, roegel@lorraine.loria.fr
Subject: Re: TraceRot?
Date: Fri, 3 Nov 2000 16:25:59 +0100 (MET) [thread overview]
Message-ID: <200011031525.QAA00614@bar.loria.fr> (raw)
In-Reply-To: <3.0.6.32.20001102141223.00a34100@pop.wxs.nl> from "Hans Hagen" at Nov 02, 2000 02:12:23 PM
`Hans Hagen' wrote
> >However, I still can't manage to make TraceRot work.
> >Below is my exact example. I do not see tha characters
> >framed.
> >
> >Denis
> >
> >\def\processfollowingtoken#1%
> >\def\followtokens#1%
>
> These are defined in the loaded library, you must omit these defs.
Actually, when I omit the two definitions it works, so I guess
there was an error in my definitions.
Denis
next prev parent reply other threads:[~2000-11-03 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 12:32 TraceRot? Denis B. Roegel
2000-11-02 13:12 ` TraceRot? Hans Hagen
2000-11-03 15:25 ` Denis B. Roegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-02 1:46 TraceRot? Denis B. Roegel
2000-11-02 10:22 ` TraceRot? 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=200011031525.QAA00614@bar.loria.fr \
--to=denis.roegel@loria.fr \
--cc=ntg-context@ntg.nl \
--cc=roegel@lorraine.loria.fr \
/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).