From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: ToC problem
Date: Mon, 06 Feb 2006 16:16:35 +0100 [thread overview]
Message-ID: <43E76853.1090409@elvenkind.com> (raw)
In-Reply-To: <e65d34bf0602060608p75375b3es@mail.gmail.com>
Elliot Clifton wrote:
> Hi Taco,
>
> Thanks for the suggestion. It looks good.
>
> I set up a test document, and cut and pased your example. Alas, it
> won't compile.
> Any idea what's wrong?
My mistake, sorry.
You need and \expanded around the call to \Article, because
otherwise the macro names \ArticleAuthor etc. end up in the
list instead of their content. So please change that line to:
\expanded{\Article{\ArticleTitle -- \ArticleAuthor}}
(you have to delete the current .tuo file also to make the
error go away)
Cheers, Taco
next prev parent reply other threads:[~2006-02-06 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 14:08 Elliot Clifton
2006-02-06 15:16 ` Taco Hoekwater [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-12 11:26 Elliot Clifton
2006-02-11 16:49 Elliot Clifton
2006-02-12 10:42 ` Taco Hoekwater
2006-02-06 18:10 Elliot Clifton
2006-02-05 23:04 Elliot Clifton
2006-02-06 10:18 ` Taco Hoekwater
2006-02-05 0:30 ToC Problem Elliot Clifton
2006-02-05 11:45 ` Taco Hoekwater
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=43E76853.1090409@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).