ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Kip Warner <kip@thevertigo.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Preserving Output Files
Date: Fri, 09 Dec 2011 20:26:40 +0100	[thread overview]
Message-ID: <4EE260F0.10402@wxs.nl> (raw)
In-Reply-To: <1323458386.16788.5.camel@kip-laptop>

On 9-12-2011 20:19, Kip Warner wrote:
> On Fri, 2011-12-09 at 18:39 +0100, Hans Hagen wrote:
>> On 6-12-2011 04:27, Kip Warner wrote:
>>> Hey list,
>>>
>>> I've searched the list, but couldn't seem to dig up anything that I
>>> thought was relevant.
>>>
>>> How do I get ConTeXt to preserve all files necessary to run the same
>>> invocation of LuaTeX it executed when it was run. As an example, when I
>>> run the following...
>>>
>>> $ context Source/Handbook.tex --result=Handbook.pdf
>>>
>>> ....it says that it ran the following...
>>>
>>> luatex
>>> --fmt="/home/kip/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/formats/cont-en" --lua="/home/kip/.texmf-var/luatex-cache/context/e570cb3e0e3ab0118ca08dd148bbec7d/formats/cont-en.lui" --backend="pdf" "Handbook.tex"
>>>
>>> If I run the same luatex command on its own, it cannot find the
>>> temporary working files passed to it in its parameters. I tried running
>>> ConTeXt with the --keep argument, but those temporary files were still
>>> not preserved.
>>
>> what temporary files?
>
> The ones luatex needs to access as you can see in the above command it
> executes as invoked by ConTeXt.

I only see

cont-en.fmt  : format file, sits in the cache and stays there
cont-en.lui  : lua startup stub, idem

handbook.tex : your file, is kept where it is

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
___________________________________________________________________________________


  reply	other threads:[~2011-12-09 19:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  3:27 Kip Warner
2011-12-09 17:39 ` Hans Hagen
2011-12-09 19:19   ` Kip Warner
2011-12-09 19:26     ` Hans Hagen [this message]
2011-12-13  3:45       ` Kip Warner
2011-12-13  9:15         ` Hans Hagen
2011-12-13 18:25           ` Kip Warner
2011-12-13 22:51             ` Hans Hagen
2011-12-14  0:58               ` Kip Warner

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=4EE260F0.10402@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=kip@thevertigo.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).