From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: MkIV missing?
Date: Mon, 4 Oct 2021 13:06:02 +0200 [thread overview]
Message-ID: <df51a7e5-6476-34c8-e14b-ecc7ef73fdd5@xs4all.nl> (raw)
In-Reply-To: <AD1824E2-C370-4E42-B716-6A8E02DE76E0@fiee.net>
On 10/4/2021 12:39 PM, Henning Hraban Ramm via ntg-context wrote:
> Hi,
> since a while, I can’t run MkIV any more, even after several runs of install.sh (and mtxrun --generate, of course).
> It’s the same on my Mac and my Linux laptop (of course the bin dir is different on the latter):
>
> $ context --version
> mtx-context | ConTeXt Process Management 1.04
> mtx-context |
> mtx-context | main context file: /Users/hraban/lmtx/tex/texmf-context/tex/context/base/mkiv/context.mkiv
> mtx-context | current version: 2021.09.26 17:00
> mtx-context | main context file: /Users/hraban/lmtx/tex/texmf-context/tex/context/base/mkxl/context.mkxl
> mtx-context | current version: 2021.09.26 17:00
>
> $ context --version --luatex
> mtx-context | redirect luametatex -> luatex: luatex --luaonly "/Users/hraban/lmtx/tex/texmf-osx-64/bin/mtxrun.lua" --script mtx-context --version --luatex --redirected
> mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
>
> $ which context
> /Users/hraban/lmtx/tex/texmf-osx-64/bin/context
>
> $ which luatex
> /Users/hraban/lmtx/tex/texmf-osx-64/bin/luatex
>
> $ luatex --version
> This is LuaTeX, Version 1.13.0 (TeX Live 2021)
> ...
>
> $ mtxrun --version
> mtxrun | ConTeXt TDS Runner Tool 1.32
> mtxrun | source path
>
>
>
> I thought that was related to the server/provider move, but I guess it isn’t.
>
> It’s a bit annoying that install.sh leaves ~/lmtx/bin in the PATH, so that a call to mtxrun can’t find any configuration.
works here ... maybe a --generate issue?
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-10-04 11:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:39 Henning Hraban Ramm via ntg-context
2021-10-04 11:06 ` Hans Hagen via ntg-context [this message]
2021-10-04 11:55 ` Henning Hraban Ramm via ntg-context
2021-10-04 13:28 ` Marcus Vinicius Mesquita via ntg-context
2021-10-04 13:33 ` Taco Hoekwater via ntg-context
2021-10-04 13:45 ` Henning Hraban Ramm via ntg-context
2021-10-04 13:50 ` Taco Hoekwater via ntg-context
2021-10-04 15:16 ` Marcus Vinicius Mesquita via ntg-context
2021-10-18 15:27 ` Jörg Hofmann via ntg-context
2021-10-19 17:09 ` Jörg Hofmann via ntg-context
2021-10-04 11:20 ` Taco Hoekwater via ntg-context
2021-10-04 11:51 ` Henning Hraban Ramm via ntg-context
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=df51a7e5-6476-34c8-e14b-ecc7ef73fdd5@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).