From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How can I use ConTeXt from TeXLive2020 ?
Date: Tue, 11 Aug 2020 00:02:40 +0200 [thread overview]
Message-ID: <2A007EDE-F941-4C2A-BB98-6BFAB54914FA@gmail.com> (raw)
In-Reply-To: <764DD6CF-11F0-47E4-8264-2644DFAD3E58@axelkielhorn.de>
Hi Axel,
> On 10 Aug 2020, at 16:11, Axel Kielhorn <tex@axelkielhorn.de> wrote:
> […]
> Well, one more suggestion:
> Use TeX Live Manager to update TeX-Live.
> I didn’t see any comments about context not working, but maybe the update fixes something.
> (You can filter for context related packages.)
>
> There has been one update to „context“ in June 2020.
I did update TeXLive with TeX Live Manager. But still I cannot run ConTeXt from TeXLive2020 (neither from TeXShop nor from Terminal).
> […]
> And another one:
> Please look into the home directory for a local .texlive2020 folder.
> There shouldn’t be any and it shouldn’t contain anything context related.
I checked for the existence of directories of the type .texlive2020: there is no such directory in my home directory.
There were three leftover directories .texlive2008, .texlive2010 and .texlive2019, which I removed.
Doing
mtxrun --generate
creates a .texlive2019 directory which contains some other folders which are
texmf-var/luatex-cache/context/88aacfe88c3cbee9a12d5f4bec4da90b/trees/
and in the latter folder there are 10 files with suffixes .lua and .luc.
Again
context test.tex
results in
mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
So the problem remains…
Best regards: Otared
___________________________________________________________________________________
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:[~2020-08-10 22:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 10:03 Otared Kavian
2020-08-10 10:37 ` Taco Hoekwater
2020-08-10 10:39 ` Axel Kielhorn
2020-08-10 12:59 ` Otared Kavian
2020-08-10 13:07 ` Taco Hoekwater
2020-08-10 13:20 ` Hans Hagen
2020-08-10 14:08 ` Otared Kavian
2020-08-10 14:15 ` Axel Kielhorn
2020-08-10 14:11 ` Axel Kielhorn
2020-08-10 22:02 ` Otared Kavian [this message]
[not found] ` <CABaoHuseyOm++oDmxjmJteZHXjA+JnV8+yEwb1rnzZWEC=c09w@mail.gmail.com>
2020-08-11 14:57 ` Otared Kavian
2020-08-11 15:25 ` Hans Hagen
2020-08-11 20:38 ` Otared Kavian
2020-08-12 6:26 ` Axel Kielhorn
2020-08-13 9:04 ` Otared Kavian
2020-08-13 10:42 ` Axel Kielhorn
2020-08-13 14:57 ` Mojca Miklavec
2020-08-14 7:43 ` Otared Kavian
2020-08-14 9:42 ` Mojca Miklavec
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=2A007EDE-F941-4C2A-BB98-6BFAB54914FA@gmail.com \
--to=otared@gmail.com \
--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).