From: Patrick Gundlach <pg@levana.de>
Subject: Re: definehead and section=
Date: Fri, 2 Nov 2001 21:35:24 +0100 [thread overview]
Message-ID: <01110221352400.00680@levana> (raw)
In-Reply-To: <5.1.0.14.1.20011102183010.0317c618@server-1>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 357 bytes --]
Good evening:
> >one more problem: why doesn't the placelist work ok after
> >\Hipart?
[...]
> do you mean the fact that it aborts the run due to uppercase? I'll look
> into it
thanks. It works perfectly smooth now :) This shows me again how little
insight I have in context and the TeX expansion mechanism...
--
Viele Grüße,
Patrick Gundlach
next prev parent reply other threads:[~2001-11-02 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Wed, 31 Oct 2001 10:27:51 +0100." <5.1.0.14.1.20011031102548.031d6828@server-1>
2001-11-02 15:17 ` Patrick Gundlach
2001-11-02 17:44 ` Hans Hagen
2001-11-02 20:35 ` Patrick Gundlach [this message]
2001-11-02 13:47 Patrick Gundlach
-- strict thread matches above, loose matches on Subject: below --
2001-10-30 16:38 Patrick Gundlach
2001-10-31 9:27 ` 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=01110221352400.00680@levana \
--to=pg@levana.de \
/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).