From: "Uwe Koloska" <uwe.koloska@mailbox.tu-dresden.de>
Subject: more problems ;-)
Date: Thu, 8 Feb 2001 19:03:00 +0100 [thread overview]
Message-ID: <01020819030002.01342@bilbo> (raw)
Hello,
1. \page[disable] seems not only to disable the next pagebreak -- it
affects all following \page commands. Is this right? And is there
a setting that only affects the next \page?
Why? In the FAQ there is a pagebreak before each new question. Til I
implement some better alternative for structuring I want to write
\section{} and have no pagebreak after the section. So I used
\setuphead[section][after={\blank[disable]}] but then all pagebreaks
are disabled. So I have to add at the start of a question
\page[reset,yes].
is it possible to force a pagebreak? I want to force every section on a
new page. With the above settings, the section break is disabled by the
former section command if there is no question ...
2. What's wrong with
\define[1]\command{\type{#1}}
\command{\par}
I get the error:
Runaway argument?
{
! Paragraph ended before \command was complete.
<to be read again>
\par
l.39 \command{\par
}).
but \type{\par} works as expected. The text is inside a block. Maybe
that's the reason. But how can \command be defined to work right.
Uwe
--
mailto:koloska@rcs.urz.tu-dresden.de
http://rcswww.urz.tu-dresden.de/~koloska/
-- --
right now the web page is in german only
but this will change as time goes by ;-)
next reply other threads:[~2001-02-08 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 18:03 Uwe Koloska [this message]
2001-02-09 7:23 ` Taco Hoekwater
2001-02-09 9:51 ` 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=01020819030002.01342@bilbo \
--to=uwe.koloska@mailbox.tu-dresden.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).