From: Roger Mason <rmason@mun.ca>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: FreeBSD 13.2
Date: Mon, 26 Feb 2024 09:47:20 -0330 [thread overview]
Message-ID: <y654jdv5pjx.fsf@mun.ca> (raw)
In-Reply-To: <a9f57b96-0bc3-4544-8cbb-193ec71f1b73@fiee.net>
Hello Hraban,
Henning Hraban Ramm <texml@fiee.net> writes:
> Usually, you don’t need to set any variables.
> The default configuration file is also fine.
>
> Does "context --version" work?
No:
mtxrun | forcing cache reload
resolvers | resolving | configuration files already identified
resolvers | resolving | skipping configuration file 'selfautoparent:/texmf-context/web2c/texmfcnf.lua' (no valid format)
resolvers | resolving | no texmf paths are defined (using TEXMF)
resolvers | resolving |
mtxrun | the resolver databases are not present or outdated
resolvers | resolving | using suffix based filetype 'lua'
resolvers | resolving | remembering file 'mtx-context.lua' using hash 'lua::mtx-context.lua'
resolvers | resolving | using suffix based filetype 'lua'
resolvers | resolving | remembering file 'mtx-contexts.lua' using hash 'lua::mtx-contexts.lua'
resolvers | resolving | remembered file 'mtx-context.lua'
resolvers | resolving | using suffix based filetype 'lua'
resolvers | resolving | remembering file 'mtx-t-mtx-context.lua' using hash 'lua::mtx-t-mtx-context.lua'
resolvers | resolving | using suffix based filetype 'lua'
resolvers | resolving | remembering file 'mtx-t-mtx-contexts.lua' using hash 'lua::mtx-t-mtx-contexts.lua'
resolvers | resolving | remembered file 'mtx-t-mtx-context.lua'
resolvers | resolving | remembered file 'mtx-context.lua'
mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
Thanks to all who have helped, but I think it is time to give up on
context. I know that context is updated often and I do not relish the
prospect of going though all this for every update.
Thanks again & best wishes,
Roger
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / 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
___________________________________________________________________________________
next prev parent reply other threads:[~2024-02-26 13:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 14:20 [NTG-context] " Roger Mason
2024-02-24 14:43 ` [NTG-context] " Henning Hraban Ramm
2024-02-24 15:28 ` Mojca Miklavec
2024-02-25 12:12 ` Hans Hagen
2024-02-25 12:17 ` Mojca Miklavec
2024-02-25 13:23 ` Henning Hraban Ramm
2024-02-28 13:29 ` Alan Braslau via ntg-context
2024-02-29 16:50 ` Roger Mason
2024-02-25 13:13 ` Roger Mason
2024-02-25 16:08 ` Roger Mason
2024-02-25 16:56 ` Henning Hraban Ramm
2024-02-25 19:24 ` Roger Mason
2024-02-25 20:47 ` Henning Hraban Ramm
2024-02-26 11:22 ` Roger Mason
2024-02-26 12:08 ` Henning Hraban Ramm
2024-02-26 13:17 ` Roger Mason [this message]
2024-02-26 12:10 ` Hans Hagen
2024-02-26 13:21 ` Roger Mason
2024-02-27 20:04 ` Hans Hagen
2024-02-29 16:47 ` Roger Mason
2024-03-22 19:07 ` Roger Mason
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=y654jdv5pjx.fsf@mun.ca \
--to=rmason@mun.ca \
--cc=ntg-context@ntg.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).