ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Felix Krause" <contact@flyx.org>
To: ntg-context@ntg.nl
Subject: Error setting up ConTeXt in MacTeX 2020
Date: Fri, 18 Sep 2020 09:41:23 +0200	[thread overview]
Message-ID: <DAB5FEE2-4730-49A3-ABBB-B76340FCA7B5@flyx.org> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1765 bytes --]

Hi all,

with MacTeX 2020 on a newly installed Mac, I have the problem that 
ConTeXt doesn't work anymore:

     $ context file.tex
     mtx-context     | warning: no format found, forcing remake 
(commandline driven)
     […] snip lots of lines
     resolvers       | formats | changing to format path 
'/var/folders/rj/hfjmjx796q102y4v23vh038c0000gp/T/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex'
     resolvers       | formats | unable to change to format path 
'/var/folders/rj/hfjmjx796q102y4v23vh038c0000gp/T/luatex-cache/context/a86c089b384a3076dc514ba966a1fac9/formats/luatex'
     mtx-context     | error, no format found with name: cont-en, 
aborting
     system          | total runtime: 5.315 seconds

The [ConTeXt docs][1] say that I should run `mtxrun --generate`, which 
seems to run successfully, and `context --make`, which finishes with the 
same „unable to change format path“ error (I believe this is what 
context automatically does when compiling my file, hinted by the „no 
format found. forcing remake“ message). I tried explicitly running 
`context --make cont-en` which yields the same result. The given path 
does exist on my hard drive.

I don't even know if the „unable to change format path“ message is 
actually an error, but I have no other indicator of what goes wrong. The 
only line that explicitly says „error“ is the one I get when trying 
to process the file.

Interestingly, I have another Mac where I upgraded from MacTeX 2019 to 
MacTeX 2020 and everything works there.

I made sure that everything is up-to-date with the TeX Live Utility.

How can I fix this problem?

Regards,
Felix


  [1]: https://wiki.contextgarden.net/Running_Mark_IV

[-- Attachment #1.2: Type: text/html, Size: 2699 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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:[~2020-09-18  7:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  7:41 Felix Krause [this message]
2020-09-18  9:20 ` Otared Kavian
2020-09-18  9:35   ` Felix Krause
2020-09-18  9:43     ` Thomas A. Schmitz
2020-09-18 10:00       ` Felix Krause
2020-09-18 10:36         ` Thomas A. Schmitz
2020-09-18 11:40           ` Felix Krause
2020-09-18  9:45 ` Henning Hraban Ramm
2020-09-18 10:02   ` Felix Krause
2020-09-18 10:50 ` Arthur Rosendahl
2020-09-18 11:48   ` Felix Krause
2020-09-18 12:49     ` Arthur Reutenauer
2020-09-18 18:28       ` Hans Hagen

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=DAB5FEE2-4730-49A3-ABBB-B76340FCA7B5@flyx.org \
    --to=contact@flyx.org \
    --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).