From: "L.S.-Soc&Gam" <axteffekt@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: A way to clean up unnecessary files after compilation in CTX mkiv
Date: Thu, 7 Apr 2016 12:55:59 +0200 [thread overview]
Message-ID: <57063CBF.8010108@gmail.com> (raw)
In-Reply-To: <5706328B.6020806@wxs.nl>
Thanks Hans,
it works. But there is a problem.
The way you described it, the *.synctex file gets deleted as well, but I
think I need it for Sumatra PDF to sync. When I used texmfstart.exe and
--purgeall this didn't happen.
Any idea would be great.
Thanks in advance,
Sebastian
Am 07.04.2016 um 12:12 schrieb Hans Hagen:
> On 4/7/2016 11:21 AM, L.S.-Soc&Gam wrote:
>> Hi guys,
>>
>> i am using mkiv with TeXnicCenter. There is an option to create a
>> clean-up processor which deletes temporary files.
>> Right now for me the options look as following:
>> Executable: X:\ConTeXt\tex\texmf-win64\bin\texmfstart.exe
>> Arguments: texutil.rb --purgeall
>> This is from an old installation instruction from mkii and works great
>> but it makes it necessary to install Ruby.
>> Since I don't want to install Ruby if it's unnecessary, i'd like to know
>> if there is a way to clean up files without mkii and Ruby elements.
>> I thought it might be possible to use *context.exe* as processor
>> executable for deleting temp files, but i wouldn't know the correct
>> arguments.
>> Sorry if I missed something obvious.
>
> assuming you run context mkiv:
>
> context --purge somefile.tex
>
> will cleanup afterwards
>
> or without file it will cleanup all left-overs
>
> (btw, the number of runtime generated files is not that large for
> mkiv: a tuc file for multipass, and a log file and of course the
> result pdf file)
>
> Hans
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2016-04-07 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 8:25 server Thomas A. Schmitz
2016-04-07 9:20 ` server Mojca Miklavec
2016-04-07 9:41 ` server Thomas A. Schmitz
2016-04-07 9:21 ` A way to clean up unnecessary files after compilation in CTX mkiv L.S.-Soc&Gam
2016-04-07 10:12 ` Hans Hagen
2016-04-07 10:55 ` L.S.-Soc&Gam [this message]
2016-04-07 13:13 ` 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=57063CBF.8010108@gmail.com \
--to=axteffekt@gmail.com \
--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).