ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: jbf <roma83537@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: --luatex option failing
Date: Fri, 28 May 2021 19:40:10 +1000	[thread overview]
Message-ID: <389f82b2-2137-ce60-f3b4-6d104fc5aefe@gmail.com> (raw)
In-Reply-To: <e701e853-87f2-9e36-5c82-c3fed08a3ecc@xs4all.nl>

Still finding it very difficult to nail what the real problem is. You 
say: "An mtxrun --generate or even context --generate should work ok. if 
not there's something with permissions or paths or a missing file".

Neither of the --generate options make any difference, so it clearly has 
to come down to "permissions or paths or a missing file". I cannot see 
that it is permissions. Comparing permissions on both machines (one 
working with --luatex and one not) I cannot see any difference. Paths? 
The only thing I can see is that I also have (later in the path) a 
separate installation for mkiv... but surely that would not make a 
difference? So, a missing file??

I renamed the current folder called lmtx so it would not be recognised 
(called it lmtxx) and created a new lmtx folder into which I have 
installed a new version (and obviously it would still be in the path, 
since ~/Documents/lmtx/tex/texmf-linux-64/bin is already in the path).

So two questions: (1) Is it possible that having another version (mkiv) 
later in the path is causing the problem? (2) If a file is missing, what 
could it possibly be, given that I did a fresh install?

As this may be an 'ignorant' kind of question, something I should really 
know but don't, about paths and permissions, there may be someone else 
on the list with time (in lockdown like I am) to put me right.

Julian

On 28/5/21 5:15 pm, Hans Hagen wrote:
> On 5/28/2021 7:13 AM, jbf wrote:
>> Hi list,
>>
>> Not at all sure why this is happening. In my most recent install of 
>> lmtx (which works fine as lmtx) on Linux, I wanted to choose the 
>> --luatex option just to make a comparison between the mkiv output and 
>> lmtx.
>>
>> The redirection part seems to work (... --script mtx-context --luatex 
>> myfile.tex --redirected), but no 'resolvers' follow. Instead I get 
>> mtxrun  | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'.
>>
>> I have tried both luatextools --generate and mtxrun --generate, but 
>> neither of these fix the problem. Would someone know why this is not 
>> working? Or even better, how to fix it? I installed lmtx on another 
>> machine and have no problems using the --luatex option there, so the 
>> matter is not urgent for me, just puzzling! I do have a separate mkiv 
>> installation as well, but my understanding is that they would not 
>> conflict. LMTX contains everything that is needed.
> In lmtx "mtxrun" and "context" are just links to "luametatex" and when 
> called with a different name than "luametatex" they will try to locate 
> scripts with their name in the same path (so there need to be 
> mtxrun.lua and context.lua in that nin path). The mtxrun.lua file 
> contains most lua libs so it can provide the same helpers as in 
> context, when used as stand alone runner (so, instead if native lua 
> one can just use mtxrun) while the context.lua script will locate 
> mtx-context.lua and run that one. For that it needs the file database.
>
> Forget about luatools .. gone for ages. An mtxrun --generate or even 
> context --generate should work ok. if not there's somethign with 
> permissions or paths or a missing file.
>
> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-05-28  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28  5:13 jbf
2021-05-28  7:15 ` Hans Hagen
2021-05-28  9:40   ` jbf [this message]
2021-05-28 10:00     ` Hans Hagen
2021-05-28 17:43       ` Pablo Rodriguez

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=389f82b2-2137-ce60-f3b4-6d104fc5aefe@gmail.com \
    --to=roma83537@gmail.com \
    --cc=j.hagen@xs4all.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).