ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: Jeong Dal <haksan@me.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: problem with a new installation of LMTX
Date: Sun, 8 Dec 2019 00:35:13 +0100	[thread overview]
Message-ID: <a83e83ce-edbe-2cfe-ff46-c7e0247bfb6a@xs4all.nl> (raw)
In-Reply-To: <35A6F20C-4F7A-4654-959F-D0D9E624AA67@me.com>

On 12/8/2019 12:20 AM, Jeong Dal wrote:
> Dear Hans, Otared,
> 
> Thank you for your concern.
> 
> The version of luametatex is 20191206.
> I followed what Otared said, but texmf-cache is not created after mtxrun.
> 
> "context —make"  is running, but no format.
> 
> I checked folders after the installation.
> Folders, texmf-cache, texmf-fonts, texmf-local, texmf-modules, texmf-project are empty.
> texmf folder contains {fonts,metapost, tex,web2c}
> texmf-context folder contains {colors,context,doc}
> However, I couldn’t find base files, script files, etc.
> Is it normal? Is it related with Catalina?
I have no clue. Normally there is a check if directories can be accessed 
and written to, so where then do these files go to?

I fear that other mac users have to help (no new mac here). Maybe Mojca 
knows as she knows all there is to know.

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:[~2019-12-07 23:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1575716401.11346.ntg-context@ntg.nl>
2019-12-07 14:11 ` Jeong Dal
2019-12-07 15:16   ` Hans Hagen
2019-12-07 23:20     ` Jeong Dal
2019-12-07 23:35       ` Hans Hagen [this message]
2019-12-08 16:30         ` Alan Braslau
2019-12-09  1:03           ` Jeong Dal
2019-12-08 20:07         ` Mojca Miklavec
2019-12-08  7:08       ` Otared Kavian
2019-12-08  7:36         ` Richard Mahoney | Indica et Buddhica
     [not found]           ` <dcf18d57-eeb1-41b8-28b0-1a9c518e4250@xs4all.nl>
2019-12-08 18:12             ` Richard Mahoney | Indica et Buddhica
2019-12-07 15:44   ` Otared Kavian
2019-12-07 19:39     ` Hans Hagen
2019-12-07 21:01       ` Otared Kavian
     [not found] <mailman.231.1575790766.1207.ntg-context@ntg.nl>
2019-12-08  8:12 ` Jeong Dal
2019-12-08  9:48   ` Floris van Manen
2019-12-08 11:15   ` Otared Kavian
2019-12-08 16:35     ` Alan Braslau
2019-12-08 17:00       ` Floris van Manen
2019-12-08 20:02       ` Mojca Miklavec
2019-12-08 12:31 ` Jeong Dal
     [not found]   ` <F146037B-D750-407F-AA4F-37D9410A4F27@gmail.com>
2019-12-09  1:03     ` Jeong Dal

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=a83e83ce-edbe-2cfe-ff46-c7e0247bfb6a@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=haksan@me.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).