From: Carlos via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Carlos <linguafalsa@gmail.com>
Subject: Re: registered function call [1160]:...live/2023/texmf-dist/tex/context/base/mkiv/l-sandbox.lua:87: cannot open /.: Permission denied - Alpine Linux
Date: Sun, 26 Mar 2023 19:38:50 -0400 [thread overview]
Message-ID: <20230326233850.jbhdy2sbejf7mprj@gmail.com> (raw)
In-Reply-To: <dd9f7710-816f-7977-f049-d42cb542e7d4@fiee.net>
On Sun, Mar 26, 2023 at 01:04:30PM +0200, Henning Hraban Ramm via ntg-context wrote:
> Am 25.03.23 um 23:42 schrieb Carlos via ntg-context:
>
> > > > fonts | names | 3092 afm files checked, okay
> > > > fonts | names | identifying tree font files with suffix 'AFM'
> > > > fonts | names | scanning path '/home/ce/.texlive2023/texmf-config' for AFM files
>
> > > > fonts | names | variable 'OSFONTDIR' specifies path '/home/ce'
> > > > fonts | names | variable 'OSFONTDIR' specifies path '/usr/share/fonts'
> > > > fonts | names | globbing path '/home/ce/**.otf'
>
> There is something strange here.
> Is maybe TEXMFHOME set?
>
> Since you use a TeX live installation, some other texmfcnf.lua or texmf.cnf
> might interfere.
> Look into /usr/local/texlive/2023/
>
> Since it scans everything in your home directory, maybe TEXMFHOME or
> OSFONTDIR is set to ~ (instead ~/texmf) there?
>
> Hraban
I created an entirely different folder and placed the otf files right in it following Hans' advice on using directly otf rather than ttf
The latter was used successfully under Void TeXLive prepackaged 2021 using a loadmapfile[texnansi-bandh-lucida.map]
There was a texmfcnf.lua under the TEXMFLOCAL variable, and another one under TEXMFDIST. Got rid of the former but haven't tested it enough.
Thanks for bringing it up!
It compiled fine, saved some rendering presumably from missing a few otf files that I didn't have under Alpine.
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
--
!07/11 PDP a ni deppart m'I !pleH
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-03-26 23:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 19:55 Carlos via ntg-context
2023-03-25 20:26 ` Hans Hagen via ntg-context
2023-03-25 20:46 ` Carlos via ntg-context
2023-03-26 23:25 ` Carlos via ntg-context
2023-03-27 13:31 ` Carlos via ntg-context
2023-03-27 13:43 ` Hans Hagen via ntg-context
2023-03-28 17:05 ` Carlos via ntg-context
2023-03-28 22:48 ` Hans Hagen via ntg-context
2023-03-31 11:40 ` Carlos via ntg-context
2023-03-31 14:40 ` Hans Hagen via ntg-context
2023-03-31 20:08 ` Carlos via ntg-context
2023-03-31 20:22 ` Hans Hagen via ntg-context
2023-04-01 21:21 ` Carlos via ntg-context
2023-04-02 8:41 ` Hans Hagen via ntg-context
2023-04-05 9:28 ` Carlos via ntg-context
2023-03-25 20:45 ` Hans Hagen via ntg-context
2023-03-25 21:36 ` Carlos via ntg-context
2023-03-25 22:09 ` Hans Hagen via ntg-context
2023-03-25 22:42 ` Carlos via ntg-context
2023-03-26 11:04 ` Henning Hraban Ramm via ntg-context
2023-03-26 13:08 ` Carlos via ntg-context
2023-03-26 13:21 ` Hans Hagen via ntg-context
2023-03-26 19:50 ` Carlos via ntg-context
2023-03-26 23:38 ` Carlos via ntg-context [this message]
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=20230326233850.jbhdy2sbejf7mprj@gmail.com \
--to=ntg-context@ntg.nl \
--cc=linguafalsa@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).