ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Missing file.tuc with setuparranging[2SIDE]
Date: Fri, 16 Nov 2012 23:37:23 +0100	[thread overview]
Message-ID: <50A6C023.9080504@wxs.nl> (raw)
In-Reply-To: <801A96D5-12A3-4B90-8D9A-E98EA452B24D@ecp.fr>

On 11/15/2012 7:35 PM, Jean-Philippe Rey wrote:
> Hi,
>
> Le 15 nov. 2012 à 17:56, Romain Diss a écrit :
>
>> Hi
>> Le jeudi 15 novembre 2012, Wolfgang Schuster a écrit :
>>> Am 15.11.2012 um 01:28 schrieb Romain Diss <romain.diss@yahoo.fr>:
>>>> I found a strange problem using \setuparranging[2SIDE] : the .tuc file is
>>>> not created anymore and this lead to a missing section number (for the
>>>> first section only). How can I remedy to that ? Any idea ?
>>>
>>> Use “context --arrange <filename>”.
>> Thank you, it seems trivial but it works well.
>>
>> Do the use of \setuparranging should always be accompanied by "context --
>> arrange <filename>" or are there specific cases?
>
>
> I don't know the official answer but I can tell you that I have been using --arrange systematically, whether or not my tex files contain \setuparranging, and I didn't notice a problem in two years. On the contrary forgetting --arrange led to problems in page numbers, references, running headers, etc.

--arrange will

(1) do an normal run and signal context to ignore \setuparranging
(2) do a final run with arranging enabled but no tuc file being written

That way the used tuc file is the right one, and not the one resulting 
from the reshuffling (a different order of flushing gives also different 
references, list ordering etc)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2012-11-16 22:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15  0:28 Romain Diss
2012-11-15  4:01 ` Wolfgang Schuster
2012-11-15 16:56   ` Romain Diss
2012-11-15 18:35     ` Jean-Philippe Rey
2012-11-16 22:37       ` Hans Hagen [this message]

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=50A6C023.9080504@wxs.nl \
    --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).