ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: jbf <roma83537@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: --luatex option failing
Date: Fri, 28 May 2021 12:00:28 +0200	[thread overview]
Message-ID: <11e0e8c6-1858-f11f-6bff-c4720ec91d77@xs4all.nl> (raw)
In-Reply-To: <389f82b2-2137-ce60-f3b4-6d104fc5aefe@gmail.com>

On 5/28/2021 11:40 AM, jbf wrote:
> 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?

not really, because the location where the running bin is found is 
determining the root of the to be used tds .. (i assume your cache is in 
that tree, not in some /tmp although even then the hashed name should 
prevent clashes)

> 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.
you need help from a linux expert indeed

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 10:00 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
2021-05-28 10:00     ` Hans Hagen [this message]
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=11e0e8c6-1858-f11f-6bff-c4720ec91d77@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=roma83537@gmail.com \
    /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).