From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: finishing a module
Date: Sun, 23 Jan 2005 16:22:54 +0100 [thread overview]
Message-ID: <41F3C14E.2020603@elvenkind.com> (raw)
In-Reply-To: <02549B04-6D4D-11D9-B338-000A95B9ADE2@uni-bonn.de>
Thomas A.Schmitz wrote:
>
> the macro \MyFont would always expand to "somefont ". But it doesn't
> seem to do so in
It should (at least until someone calls \xdef\MyFont again).
> \definefont[Gf][\MyFont]
>
> I still get the error message.
The problem is not the \MyFont \def, but in the \definefont, that is why
I thought that \expanded{\definefont[Gf][\MyFont]} should work.
And, AFAICS, it does work fine here.
Greetings, Taco
next prev parent reply other threads:[~2005-01-23 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 20:41 Thomas A.Schmitz
2005-01-23 9:33 ` Taco Hoekwater
2005-01-23 13:33 ` Thomas A.Schmitz
2005-01-23 14:06 ` Taco Hoekwater
2005-01-23 14:42 ` Thomas A.Schmitz
2005-01-23 15:22 ` Taco Hoekwater [this message]
2005-01-23 21:24 ` h h extern
2005-01-24 14:06 ` Thomas A.Schmitz
2005-01-24 17:50 ` Hans Hagen
2005-01-24 17:50 ` Hans Hagen
2005-01-24 18:20 ` Thomas A.Schmitz
2005-01-24 18:03 ` Hans Hagen
2005-01-24 18:47 ` Thomas A.Schmitz
2005-01-25 14:56 ` h h extern
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=41F3C14E.2020603@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).