From: "amano.kenji via ntg-context" <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: "amano.kenji" <amano.kenji@proton.me>
Subject: A few questions about texmfcnf.lua and mtxrun in TexLive.
Date: Sat, 20 Aug 2022 12:13:26 +0000 [thread overview]
Message-ID: <D5qmBVYgPSECwiCqKcohx6KDLzDICfx-X5bdydARv-Bo5kx3XEHSoqm8LmE_ZWqc4IGsbyPnm6tdMqndmCPzX1dMEZxDgUirTDKx4Jo82xs=@proton.me> (raw)
I'm currently using TexLive 2021 from Gentoo Linux. TexLive 2022 may behave with slight differences.
* How does /usr/share/texmf-local/web2c/texmfcnf.lua override /usr/share/texmf-dist/web2c/texmfcnf.lua? According to mtxrun --configurations, /usr/share/texmf-dist comes later than /usr/share/texmf-local. It seems to me that texmf-dist should override texmf-local.
* mtxrun --resolve-path '$SELFAUTOPARENT' resolves selfautoparent to '.' which is the current working directory if selfautodir is /usr. I think mtxrun refuses to accept '/' as selfautoparent and assigns the current working directory to selfautoparent. Is this a bug?
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2022-08-20 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='D5qmBVYgPSECwiCqKcohx6KDLzDICfx-X5bdydARv-Bo5kx3XEHSoqm8LmE_ZWqc4IGsbyPnm6tdMqndmCPzX1dMEZxDgUirTDKx4Jo82xs=@proton.me' \
--to=ntg-context@ntg.nl \
--cc=amano.kenji@proton.me \
/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).