From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: multiple lines in footers
Date: Wed, 02 Jan 2002 09:52:23 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020102094650.031aac60@server-1> (raw)
In-Reply-To: <3C31F356.7C7F7AAC@WbMT.TUDelft.NL>
At 06:35 PM 1/1/2002 +0100, Ron van Ostayen wrote:
>Hans, why do I have to use \endgraf ?
>The TeX-book says that \par and \endgraf are basically the same but if I
>use
>\par it results in an error-message, \endgraf does not.
indeed, that is why \endgraf is needed; tex is very sensitive about \par's,
one reason (probably) being that in th eold days it was a good thing to
catch an unbalanced argument (which often contains an empty line or \par).
Endgraf (which is a 'copy' of \par is not seen as a literate par
(interesting since it's a straight copy).
One way around is to define all macros in a call chain with parameters as
\long (\long\def\...). Unfortunately there is no switch to disable this
'feature'. Another funny error catcher is \outer but in context i
\let\outer\relax in an early stage so that is kind of gone.
>The left and righthand footer are now aligned on the bottom. How can I
>align
>them on the top?
\vtop
if needed add a couple of \strut's (say \showstruts to see them in action)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-01-02 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 11:08 Ron van Ostayen
2002-01-01 12:31 ` Hans Hagen
2002-01-01 17:35 ` Ron van Ostayen
2002-01-02 8:52 ` Hans Hagen [this message]
2002-01-01 12:43 ` Tobias Burnus
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=5.1.0.14.1.20020102094650.031aac60@server-1 \
--to=pragma@wxs.nl \
--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).