From: Emil Hedevang Lohse <emil@imf.au.dk>
Subject: Re: Re: #'s in MPinclusions
Date: 24 Jan 2003 14:38:38 +0100 [thread overview]
Message-ID: <vg0hebypt0h.fsf@localhost.localdomain> (raw)
In-Reply-To: <5.1.0.14.1.20030122141802.03404e18@server-1>
Hans Hagen <pragma@wxs.nl> writes:
> Your first method is the proper way:
>
> copied from supp-mps.tex:
>
> \appendtoks
> \let \# \letterhash
> \let \_ \letterunderscore
> \let \& \letterampersand
> \let \{ \letteropenbrace
> \let \} \letterclosebrace
> \to \everyMPgraphic
I believe there is a bug in supp-ini.tex:
.catcode `.} 12 .xdef .letterclosebrace B.string{E
should be
.catcode `.} 12 .xdef .letterclosebrace B.string}E
--
Emil Hedevang Lohse <http://home.imf.au.dk/emil/>
Alle spørgsmål er lige dumme.
Og spørgsmålet "Kan ænder flyve?" er ikke dumt.
next prev parent reply other threads:[~2003-01-24 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 10:21 Emil Hedevang Lohse
2003-01-22 11:54 ` Patrick Gundlach
2003-01-22 13:18 ` Hans Hagen
2003-01-24 13:38 ` Emil Hedevang Lohse [this message]
2003-01-24 14:18 ` 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=vg0hebypt0h.fsf@localhost.localdomain \
--to=emil@imf.au.dk \
--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).