From: Kip Warner <kip@thevertigo.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: Preserving Output Files
Date: Tue, 13 Dec 2011 16:58:26 -0800 [thread overview]
Message-ID: <1323824306.2324.4.camel@kip-laptop> (raw)
In-Reply-To: <4EE7D704.3080004@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 608 bytes --]
On Tue, 2011-12-13 at 23:51 +0100, Hans Hagen wrote:
> I can run the direct command here, not that I ever do it as the context
> command does some housekeeping and passes commandline info via the top
> file. There is hardly any gain in running luatex directly.
Hey Hans. I understand, but I need to be able to run luatex directly in
the same way ConTeXt is invoking it. The reason being is Mojca and I
want to get a stack trace for an issue that popped up executing on
mipsel64 hardware.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- 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
___________________________________________________________________________________
prev parent reply other threads:[~2011-12-14 0:58 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
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 [this message]
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=1323824306.2324.4.camel@kip-laptop \
--to=kip@thevertigo.com \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).