ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: --purgebufffers option?
Date: Thu, 4 Jul 2013 15:19:58 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.02.1307041515130.10806@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <51D5A671.1030301@web.de>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 795 bytes --]

On Thu, 4 Jul 2013, Pablo Rodríguez wrote:

> Dear Hans,
>
> I compile ConTeXt documents with --purgeall, but if I save buffers into
> files and typeset those files or I typeset buffers directly, these files
> aren’t purged after successful compilation.

--purgeall deletes all `*-temp-*.tmp` files from a directory. So, one 
option (that I use in the filter module) is to use that structure while 
naming your temporary files.

> Would it be possible to enable an option (such as --purgebuffers) that
> removes all buffer files generated by that compilation?

IIRC, in t-gnuplot, Mojca had used a macro to store the name of all the 
generated buffers and some test code (or maybe just the idea) to store 
them the tuc file so that they get deleted by context/texexec.

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
___________________________________________________________________________________

  reply	other threads:[~2013-07-04 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04 16:44 Pablo Rodríguez
2013-07-04 19:19 ` Aditya Mahajan [this message]
2013-07-04 20:06   ` 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.1307041515130.10806@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).