From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: installing two ConTeXt trees
Date: Wed, 04 Sep 2013 09:32:01 +0200 [thread overview]
Message-ID: <5226E1F1.9010905@wxs.nl> (raw)
In-Reply-To: <6116F93D-B129-40FE-80EF-86135D080177@gmail.com>
On 9/4/2013 9:05 AM, Otared Kavian wrote:
>
> On 3 sept. 2013, at 19:14, Aditya Mahajan <adityam@umich.edu> wrote:
>
>>> […]
>>> the synctex.gz file is not anymore deleted (however a utility file [file-name].tuc remains).
>>
>> That (not deleting tuc file) is delebrate (as it saves time in successive runs). If you want to delete the tuc file, you can use --purgeall instead of --purge.
>
> Thanks Aditya: actually that utility file .tuc can be deleted for some situations (for instance when one does a small test) and kept for others.
> Maybe for those who do not use ConTeXt from a Terminal, but rather from editors like TeXShop or TeXWorks, one could have a feature to pass typesetting options to mkiv, for instance like a \setuptypesetting command, to be put in the first five lines of a document, which accepts various parameters such as for example
> \setuptypesetting[purge=yes,synctex={yes,zipped},engine=mkiv]
>
> to pass options to mkiv. But this is probably too complicated.
the job is already running and one needs tex to parse such commands
there are two ways (rather old features btw) to control a job:
- some directives can be given on the first line of a file
- you can make a jobname.ctx file (there are a few examples in the
distribution)
the last one is the most flexible as there can be a file per job or a
shared one
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-09-04 7:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 12:12 Alan Bowen
2013-08-31 12:27 ` Hans Hagen
2013-08-31 14:46 ` Alan Bowen
2013-08-31 15:25 ` Aditya Mahajan
2013-08-31 15:24 ` Aditya Mahajan
2013-08-31 17:02 ` Alan Bowen
2013-09-01 17:54 ` Otared Kavian
2013-09-02 16:14 ` Alan Bowen
2013-09-02 21:44 ` Hans Hagen
2013-09-03 7:31 ` Otared Kavian
2013-09-03 8:50 ` Hans Hagen
2013-09-03 13:08 ` Otared Kavian
2013-09-03 17:14 ` Aditya Mahajan
2013-09-04 7:05 ` Otared Kavian
2013-09-04 7:32 ` Hans Hagen [this message]
2013-09-04 8:36 ` Hans Hagen
2013-09-06 17:04 ` Otared Kavian
2013-09-06 20:28 ` 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=5226E1F1.9010905@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).