From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: utility file
Date: Wed, 29 Nov 2006 12:35:42 +0100 [thread overview]
Message-ID: <F24FD564-F490-4110-A05D-99BE7E78AA88@uni-bonn.de> (raw)
In-Reply-To: <456CA55F.7020500@wxs.nl>
On Nov 28, 2006, at 10:08 PM, Hans Hagen wrote:
> you need to make sure that only one run takes place and no utility
> file
> is processed
>
> --arrange
>
> normally will handle this for you
>
> Hans
>
Hans,
can you elaborate on this? Some days ago, I had a problem which I
suspect had the same cause. I had prepared a bibliography for one of
my classes with Taco's module; it typset beautifully. To save paper,
I wanted to typeset two A5 pages on one A4 landscape page and used
\setuparranging[2*2,rotated]
After compiling, the bibliography was gone! I was in a hurry, so I
simply undid the arranging and reverted to real cut-and-paste, but
utility files seem like the obvious culprit.
Best
Thomas
next prev parent reply other threads:[~2006-11-29 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 20:57 Wolfgang Werners-Lucchini
2006-11-28 21:08 ` Hans Hagen
2006-11-29 11:35 ` Thomas A. Schmitz [this message]
2006-12-05 17:40 ` John R. Culleton
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=F24FD564-F490-4110-A05D-99BE7E78AA88@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).