From: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lua args or how to identify the interpreter
Date: Thu, 22 Jul 2010 12:42:14 +0200 [thread overview]
Message-ID: <20100722104214.GB7491@aides> (raw)
In-Reply-To: <4C48159A.6050101@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2326 bytes --]
On 2010-07-22 <11:55:38>, Hans Hagen wrote:
> On 22-7-2010 11:51, Philipp Gesang wrote:
> >Hi all,
> >
> >what would be an elegant way to make out the current interpreter from inside
> >lua?
> >
> >For now I'm branching things at the top of the script like this:
> >
> >···8<··········································································
> >if arg[-1] == "texlua" then
> > utf=unicode.utf8
> >else
> > require "lpeg"
> > utf=string
> >end
> >···8<··········································································
>
> if you run your script with mtxrun then you can ask for arguments using
>
> environment.argument
> environment.files
Hi Hans,
thank you, I was rather looking for some unified way of identifying the
lua interpreter that would work with the 4 machines I mentioned. Nevermind,
individually testing, while it does not really look good, works fine:
···8<··········································································
if context then
interp = "context"
elseif arg[0] == "luatex" then
interp = "luatex"
elseif arg[-1] == "texlua" then
interp = "texlua"
else
interp = "plainlua"
end
···8<··········································································
>
>
>
> -----------------------------------------------------------------
> 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
> ___________________________________________________________________________________
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 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:[~2010-07-22 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 9:51 Philipp Gesang
2010-07-22 9:55 ` Hans Hagen
2010-07-22 10:42 ` Philipp Gesang [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=20100722104214.GB7491@aides \
--to=pgesang@ix.urz.uni-heidelberg.de \
--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).