From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: precedence of texmf trees
Date: Wed, 20 Oct 2021 20:31:46 +0200 [thread overview]
Message-ID: <30D33FAE-8871-4832-B4D6-739972B6ADBB@fiee.net> (raw)
In-Reply-To: <e08ff10b-0a04-6330-a530-80c3eb91c0a8@xs4all.nl>
> Am 20.10.2021 um 16:38 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>
> On 10/20/2021 4:21 PM, Henning Hraban Ramm via ntg-context wrote:
>>> Am 20.10.2021 um 10:10 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>>>> Where is the order defined? (Not in TDS.)
>>> mtxrun --show-variables
>> Oh, yes, of course. Thank you!
>>> etc ... it's all TDS
>> I meant, the order of trees is not defined in the TDS proposal (http://tug.org/tds/tds.html).
> it's kind of defined by texlive but there it changed over time, (main, dist, local, var, home etc and also unix distributers add / patch these variables; some definitions and order can be hard coded in the binary part that deals with kpse file lookup)
I thought so...
> anyway, in context it hasn't changed much and we don’t use the kpse library in mkiv/lmtx so we're not affected by changes; you can of course add more of use a different order (in a local configuration file in e.g. texmf-local)
>
> (there are plenty of trackers for checking how files are looked up)
I just wanted to give an overview in my book what is where in all those trees, and then I recognized I didn’t know the search order.
(Yes, I’m in ConTeXt book writing mode again.)
Hraban
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-10-20 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 18:24 Henning Hraban Ramm via ntg-context
2021-10-20 8:10 ` Hans Hagen via ntg-context
2021-10-20 14:21 ` Henning Hraban Ramm via ntg-context
2021-10-20 14:38 ` Hans Hagen via ntg-context
2021-10-20 18:31 ` Henning Hraban Ramm 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=30D33FAE-8871-4832-B4D6-739972B6ADBB@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).