From: Willi Egger <w.egger@boede.nl>
Subject: texexec --arrange and texexec --noarrange
Date: Tue, 23 Dec 2003 19:49:32 +0100 [thread overview]
Message-ID: <3FE88E3C.7050601@boede.nl> (raw)
Hi Contexters,
Recently I tried to arrange pages of a document with
texexec --arrange jobname
In my environment file I setup the following:
\setuppapersize[A5,portrait][A4,landscape]
\setuppagenumbering[alternative=doublesided,location={footer}]
% Arranging:
\setuparranging[2UP]
Of course I can comment the line of the arranging and just uncomment it
for a single run hereafter to produce a PDF-file with arranged pages.
When using texexec --arrange this should happen automatically. I
realize, that the system is halted after
systems: end file jobname at line 47
textblocks: writing textblocks to jobname.tub
It looks like texexec is waiting for an input....
An identical situation occurs when issueing texexec --noarrange jobname
Am I doing something wrong or is there a bug in texexec?
Kind regards Willi
texexec --noarrange
next reply other threads:[~2003-12-23 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 18:49 Willi Egger [this message]
2004-01-04 17:22 ` Hans Hagen
2004-01-05 14:54 ` Willi Egger
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=3FE88E3C.7050601@boede.nl \
--to=w.egger@boede.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).