From: Hans van der Meer <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: mtxrun
Date: Tue, 17 Jun 2008 18:49:30 +0200 [thread overview]
Message-ID: <EAE0EB45-4737-49D3-A73B-71C6F13AB108@uva.nl> (raw)
Following the article "The luafication of TeX and Context" in the
recent issue of the NTG-MAPS I tried the example given:
mtxrun --script fonts
and this should return the options list for this script.
However, I get:
101 ~: mtxrun --script fonts
cannot open : No such file or directory
While otherwise a bare mtxrun returns info and thus was found as a
runnable script:
102 ~: mtxrun
MtxRun | version 1.0.2 - 2007+ - PRAGMA ADE / CONTEXT
MtxRun | --script run an mtx script
In my .bashrc I had the lua scripts in the path:
103 ~: echo $PATH
..:/usr/local/texlive/texmf-context/scripts/context/lua/:..
And I had called luatools --generate to make the database plus I made
certain the script has execute permissions:
/usr/local/texlive/texmf-context/scripts/context/lua/mtx-fonts.lua -
rwxr-xr-x
What is wrong or what I am doing wrong?
Hans van der Meer
___________________________________________________________________________________
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 reply other threads:[~2008-06-17 16:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 16:49 Hans van der Meer [this message]
2008-06-17 17:29 ` mtxrun Hans Hagen
2008-06-17 17:34 ` mtxrun Taco Hoekwater
2008-06-17 19:47 ` mtxrun Aditya Mahajan
2008-06-18 8:12 ` mtxrun Hans van der Meer
2008-06-18 9:37 ` mtxrun Hans Hagen
2008-06-18 11:54 ` mtxrun Taco Hoekwater
2011-01-23 16:21 MTXrun Herbert Voss
2011-01-23 17:43 ` MTXrun Vedran Miletić
2011-01-23 19:25 ` MTXrun Hans Hagen
2020-02-10 10:54 mtxrun Rudolf Bahr
2020-02-10 11:06 ` mtxrun Taco Hoekwater
2020-02-10 11:27 ` mtxrun Rudolf Bahr
2020-02-10 12:03 ` mtxrun Rudolf Bahr
2020-02-11 10:56 ` mtxrun Rudolf Bahr
2020-02-11 12:07 ` mtxrun Hans Hagen
2020-02-11 15:23 ` mtxrun Rudolf Bahr
2020-02-11 15:57 ` mtxrun Pablo Rodriguez
2020-02-11 17:26 ` mtxrun Rudolf Bahr
2020-02-11 18:38 ` mtxrun Hans Hagen
2020-02-11 20:41 ` mtxrun Rudolf Bahr
2020-02-11 20:57 ` mtxrun Aditya Mahajan
2020-02-12 5:44 ` mtxrun Rudolf Bahr
2020-02-11 18:39 ` mtxrun Aditya Mahajan
2020-02-12 4:41 ` mtxrun Rudolf Bahr
2020-02-12 5:24 ` mtxrun Aditya Mahajan
2020-02-12 10:05 ` mtxrun Rudolf Bahr
[not found] <mailman.474.1581455525.1332.ntg-context@ntg.nl>
2020-02-14 19:59 ` mtxrun Luca Donetti
2020-02-15 4:59 ` mtxrun Aditya Mahajan
2020-02-15 5:40 ` mtxrun Rudolf Bahr
2020-02-15 11:32 ` mtxrun Floris van Manen
2020-02-15 14:57 ` mtxrun Aditya Mahajan
[not found] <mailman.0.1581764401.20240.ntg-context@ntg.nl>
2020-02-15 14:38 ` mtxrun Luca Donetti
2020-02-15 14:48 ` mtxrun Luca Donetti
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=EAE0EB45-4737-49D3-A73B-71C6F13AB108@uva.nl \
--to=h.vandermeer@uva.nl \
--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).