From: Luis Rivera <jlrn77@gmail.com>
To: cygwin@cygwin.com
Subject: luatex not loading opentype fonts
Date: Thu, 22 Dec 2022 01:02:19 -0600 [thread overview]
Message-ID: <CAOEhWT097htNvmqxSysg9Wt_HVsETVxe-Fu9RJvjpNkVFkLXww@mail.gmail.com> (raw)
While developing a package for LuaTeX with the texlive-collection, I
noticed that LuaTeX could not access the directories for OpenType
fonts;
```
$ luatex sloth
This is LuaTeX, Version 1.15.0 (TeX Live 2022/Cygwin)
restricted system commands enabled.
(./sloth.tex (/home/root/.local/share/texmf/tex/luatex/luatex85.sty)
(/usr/share/texmf-dist/tex/generic/yax/yax.tex
(/usr/share/texmf-dist/tex/generic/texapi/texapi.tex))
(/usr/share/texmf-dist/tex/generic/gates/gates.tex
(/usr/share/texmf-dist/tex/generic/texapi/texapi.tex)) (./lua.ptx) (./files.ptx
) (./fonts.ptx./fonts.ptxlua:285: cannot open .:/home/root/.config/texmf/fonts/
opentype/:/home/root/.cache/texmf/fonts/opentype/:/home/root/.local/share/texmf
/fonts/opentype/:/usr/share/texmf-site/fonts/opentype/:/etc/texmf/fonts/opentyp
e/:/var/lib/texmf/fonts/opentype/:/usr/share/texmf-dist/fonts/opentype/:/home/r
oot/.config/texmf/fonts/truetype/:/home/root/.cache/texmf/fonts/truetype/:/home
/root/.local/share/texmf/fonts/truetype/:/usr/share/texmf-site/fonts/truetype/:
/etc/texmf/fonts/truetype/:/var/lib/texmf/fonts/truetype/:/usr/share/texmf-dist
/fonts/truetype/:/cygdrive/c/windows/fonts/: No such file or directory
stack traceback:
[C]: in function 'lfs.dir'
./fonts.ptxlua:285: in local 'check_fonts'
./fonts.ptxlua:366: in main chunk
[C]: in function 'dofile'
[\directlua]:1: in main chunk.
\inputluafile ...ua {dofile(kpse.find_file("#1"))}
l.1 \inputluafile fonts.ptxlua
?
```
Which is weird, because my program works correctly in the windows
version of TeXLive, and `ls /cygdrive/c/windows/fonts` returns the
directory listing correctly.
I fear I have spotted a bug.
Luis Rivera
next reply other threads:[~2022-12-22 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 7:02 Luis Rivera [this message]
2022-12-22 14:45 ` Ken Brown
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=CAOEhWT097htNvmqxSysg9Wt_HVsETVxe-Fu9RJvjpNkVFkLXww@mail.gmail.com \
--to=jlrn77@gmail.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).