Hi Hans,

On Tue, Sep 22, 2026 at 20:10 (+0200), Hans Hagen via ntg-context wrote:

> On 9/22/2026 6:01 PM, Jim Diamond via ntg-context wrote:
>> On Tue, Sep 22, 2026 at 17:05 (+0200), Hans Hagen via ntg-context wrote:

>>> Hi,

>>> A new version has been uploaded. HOpefully we fixed the reported font
>>> issues,

>> Continuing on my "is this OK or not?" theme of the day, at the beginning of
>> the update on the terminal I see

>> mtxrun          | forcing cache reload
>> resolvers       | resolving | looking for regular 'texmfcnf.lua' on given 
>> path '/home/zsd/texmf/web2c' from specification 'home:texmf/web2c'
>> resolvers       | resolving | looking for regular 'texmfcnf.lua' on given 
>> path '/usr/local/texmf-local/web2c' from specification 
>> 'selfautoparent:/texmf-local/web2c'
>> resolvers       | resolving | looking for regular 'texmfcnf.lua' on given 
>> path '/usr/local/texmf-context/web2c' from specification 
>> 'selfautoparent:/texmf-context/web2c'
>> resolvers       | resolving | looking for regular 'texmfcnf.lua' on given 
>> path '/usr/local/texmf/web2c' from specification 
>> 'selfautoparent:/texmf/web2c'

>> The first place it looks for texmfcnf.lua is reasonable, it has my home
>> directory name correct.

>> My context lives in
>>          /usr/local/context
>> but the second, third and fourth places are in
>>          /usr/local
>> instead of
>>          /usr/local/context

>> "Outside" the context tree seems (to me) like an odd put a texmfcnf.lua
>> file.

>> Is that what is intended?

> after decades of tex distributions and various iterations / permutations of
> texmf + somethign local or dist or .. i gave up on what is the intention

So far I follow you, I can see looking in a number of places.

> that said: i put my overloads in texmf-local (first variable comes, first
> wins, all these are read)

>>mtxrun --configurations
> system          | resolved | file :
> c:/data/develop/tex-context/tex/texmf-local/web2c/texmfcnf.lua
> system          | resolved | file :
> c:/data/develop/tex-context/tex/texmf/web2c/texmfcnf.lua
> system          | resolved |
> system          | resolved | path + C:/Users/Hans Hagen/texmf/web2c
> system          | resolved | path -
> c:/data/develop/tex-context/tex/texmf-local/web2c
> system          | resolved | path -
> c:/data/develop/tex-context/tex/texmf-context/web2c
> system          | resolved | path -
> c:/data/develop/tex-context/tex/texmf/web2c

These make sense, after the update is over, I get some analogous (but for
Linux) paths.  For example, the last one for me is:

system          | resolved | path - /usr/local/context/tex/texmf/web2c


But... during the update (as in my first message in this thread), the
"/usr/local" ones were missing the "context/tex/" part of those paths.
Which struck me as curious, because if I had a
        /usr/local/context/tex/texmf-local/web2c/texmfcnf.lua
file, it seems like it would not have been examined.

So perhaps I should have asked a more direct question: should any local
texmfcnf.lua file (which I want processed during rebuilds) be *above* the
directory in which context is installed, rather than under that directory?

Thanks.
                                        Jim

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / 
https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

Reply via email to