From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: gnuplot module
Date: Thu, 17 Apr 2008 16:37:55 +0200 [thread overview]
Message-ID: <6faad9f00804170737m646aa7e2j193589951aca1e86@mail.gmail.com> (raw)
In-Reply-To: <87ej94o8ua.fsf@cordelia.devereux.me.uk>
On Thu, Apr 17, 2008 at 4:27 PM, John Devereux wrote:
> "Mojca Miklavec" writes:
>
> > Do you have any suggestions about how to reduce the number of files in
> > some sensible way?
>
> The ideal would be an option when processing the source file, to turn
> off file deletion. Like
>
> texexec document.tex --keep-temporaries
>
> So by default the source directory would be kept clean, but when
> "debugging" the intermediate files would be available.
>
> Or perhaps some option passed to \startGNUPLOTscript (or
> \useGNUPLOTgraphic) if that is possible?
>
> \startGNUPLOTscript[example][keeptemporaryfile=yes]
This sounds fine (having a --debug-like option), but one more question
- what about caching existing results? (If all files are deleted, then
it's not possible to ask for --ifchanged, so gnuplot needs to be run
each time.)
> That might be better otherwise debugging a big document could result
> it hundreds of files.
>
> Another possibility would be to put the files in /tmp.
That's not too practical.
Mojca
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-17 14:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 20:53 Unable to generate luatex formats Michael Green
2008-04-13 8:02 ` Taco Hoekwater
2008-04-13 11:54 ` Hans Hagen
2008-04-13 10:12 ` Jean Magnan de Bornier
2008-04-15 7:57 ` John Devereux
2008-04-15 9:31 ` Taco Hoekwater
2008-04-15 9:44 ` John Devereux
2008-04-15 9:56 ` Hans Hagen
2008-04-15 10:37 ` John Devereux
2008-04-15 10:46 ` Mojca Miklavec
2008-04-15 11:25 ` John Devereux
2008-04-15 12:17 ` Mojca Miklavec
2008-04-15 12:52 ` John Devereux
2008-04-15 12:59 ` Mojca Miklavec
2008-04-16 15:18 ` John Devereux
2008-04-16 18:29 ` Mojca Miklavec
2008-04-16 19:24 ` gnuplot module John Devereux
2008-04-17 13:42 ` Mojca Miklavec
2008-04-17 14:23 ` Henning Hraban Ramm
2008-04-17 14:31 ` Mojca Miklavec
2008-04-17 14:27 ` John Devereux
2008-04-17 14:37 ` Mojca Miklavec [this message]
2008-04-17 15:31 ` John Devereux
2008-04-15 14:16 ` Unable to generate luatex formats Hans van der Meer
2008-04-15 14:29 ` Mojca Miklavec
2008-04-15 14:31 ` Mojca Miklavec
2008-04-15 15:00 ` Hans Hagen
2008-04-15 10:40 ` Hans van der Meer
2008-04-15 9:43 ` Mojca Miklavec
2008-04-16 10:21 ` John Devereux
2008-04-16 18:53 ` Joel C. Salomon
2008-04-16 19:01 ` Mojca Miklavec
2008-04-16 20:32 ` Hans Hagen
2008-04-17 4:55 ` Joel C. Salomon
2008-04-17 7:50 ` Taco Hoekwater
2008-04-17 8:03 ` Hans Hagen
2011-12-12 0:40 gnuplot module Mojca Miklavec
2011-12-12 0:49 ` Paul Menzel
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=6faad9f00804170737m646aa7e2j193589951aca1e86@mail.gmail.com \
--to=mojca.miklavec.lists@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).