From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: precedence of texmf trees
Date: Wed, 20 Oct 2021 16:38:16 +0200 [thread overview]
Message-ID: <e08ff10b-0a04-6330-a530-80c3eb91c0a8@xs4all.nl> (raw)
In-Reply-To: <5B42E569-0275-4029-87B5-ED32DA78FBAB@fiee.net>
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>:
>>
>> On 10/19/2021 8:24 PM, Henning Hraban Ramm via ntg-context wrote:
>>> Hi wizards,
>>> if I have files with the same name in several texmf trees (e.g. texmf-context, texmf-local, texmf-project, ~/texmf or TeX Live’s texmf-dist, texmf-var), which one will be used?
>>> I guess “local” trees or “local” directories take precedence over “distribution”, but which is “the localest” of ~/texmf/..., texmf-dist/.../local, texmf-local/... ?
>>
>>> context --generate
>>
>> show all this
>>
>>> 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)
anyway, in contest it hasn't changed much and we dont' 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)
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-10-20 14:38 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 [this message]
2021-10-20 18:31 ` Henning Hraban Ramm via ntg-context
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=e08ff10b-0a04-6330-a530-80c3eb91c0a8@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).