From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: installing two ConTeXt trees
Date: Tue, 3 Sep 2013 13:14:19 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1309031313290.25949@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <C7A1F718-7862-4209-9EDD-3EBA198D7515@gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1041 bytes --]
On Tue, 3 Sep 2013, Otared Kavian wrote:
>
> On 3 sept. 2013, at 10:50, Hans Hagen <pragma@wxs.nl> wrote:
>
>> On 9/3/2013 9:31 AM, Otared Kavian wrote:
>>> […]
>>> Thanks Hans for your attention, but saying
>>> texexec --autogenerate --synctex=1 "$1" --purge
>>>
>>> or
>>> context --autogenerate --synctex=1 "$1" --purge
>>>
>>> removes also the synctex.gz file and one loses the synctex functionality which is essential for me.
>>
>> i've added a test: if --synctex is given or the first line has
>>
>> % synctex=zipped|unzipped|1|-1|yes
>>
>> then the synctex file is not deleted
>
> Hi Hans,
>
> Thanks for the quick modification…
> I tested the new beta, and indeed using mkiv and
> context --autogenerate --synctex=1 "$1" --purge
>
> 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.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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-03 17:14 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 [this message]
2013-09-04 7:05 ` Otared Kavian
2013-09-04 7:32 ` Hans Hagen
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=alpine.LNX.2.02.1309031313290.25949@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).