From: frantisek holop <minusf@obiit.org>
Subject: Re: \page inside a block
Date: Thu, 16 Mar 2006 23:57:49 +0100 [thread overview]
Message-ID: <20060316225749.GC13262@obiit.org> (raw)
In-Reply-To: <44194036.4000500@wxs.nl>
so,
lo and behold, a beginner \TeX{}er's "solution":
-----------------------%<-------------------------
\defineparagraphs
[poem][n=2]
\setupparagraphs
[poem][1][width=.35\textwidth]
\setupparagraphs
[poem][2][rule=on]
\def\StartPoem#1{%
\startpoem
\ifx#1\undefined\else\section{#1}\fi
\poem\startlines}
\def\StopPoem{%
\stoplines\stoppoem\page}
\def\PoemPage{%
\StopPoem
\StartPoem{}}
\starttext
\StartPoem{poem1}
line 1
line 2
\StopPoem
\StartPoem{poem2}
line 1
line 2
\PoemPage
line 3
line 4
\StopPoem
\stoptext
-----------------------%<-------------------------
as the poems are quite static, and in this case it is
actually better if i can "cut" the page at a convinient
point, i think this is an easier "hack"
(at the moment for me definitely) :))))))
and it also takes care of the \startlines \stoplines
i asked about earlier. not that Taco's solution
did not work, but this is much more primitive,
and so better at the moment.
i have another question. how can i modify how the "rule"
will look like? the closest thing i have found in the
manual was \setupmarginrules but \setupmarginrules[thickness=5]
did nothing.
thanks to everyone for pointing out where the manual sources are.
-f
--
a fool searches for a greater fool to find admiration.
next prev parent reply other threads:[~2006-03-16 22:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 23:53 frantisek holop
2006-03-16 10:38 ` Hans Hagen
2006-03-16 21:50 ` frantisek holop
2006-03-16 22:17 ` Aditya Mahajan
2006-03-16 22:27 ` Thomas A. Schmitz
2006-03-16 22:57 ` frantisek holop [this message]
2006-03-17 18:49 ` Willi Egger
2006-03-26 19:42 ` \setupmarginrules (was: Re: \page inside a block) frantisek holop
2006-03-26 20:12 ` \setupmarginrules Vit Zyka
2006-03-26 20:41 ` \setupmarginrules frantisek holop
2006-03-27 20:54 ` \setupmarginrules Vit Zyka
2006-03-28 14:49 ` \setupmarginrules Willi Egger
2006-03-28 15:05 ` \setupmarginrules Taco Hoekwater
2006-03-28 15:10 ` \setupmarginrules Vit Zyka
2006-03-28 15:14 ` \setupmarginrules Taco Hoekwater
2006-03-28 16:58 ` \setupmarginrules Vit Zyka
2006-03-28 17:13 ` \setupmarginrules Hans Hagen
2006-03-30 19:18 ` \setupmarginrules Willi Egger
2006-03-28 16:42 ` \setupmarginrules Hans Hagen
2006-03-28 17:12 ` \setupmarginrules Hans Hagen
2006-03-28 18:55 ` \setupmarginrules Vit Zyka
2006-03-28 21:44 ` \setupmarginrules frantisek holop
2006-03-29 8:14 ` \setupmarginrules 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=20060316225749.GC13262@obiit.org \
--to=minusf@obiit.org \
--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).