From: Rudolf Bahr <quasi@quasi.de>
To: ntg-context@ntg.nl
Subject: Re: mtxrun
Date: Tue, 11 Feb 2020 16:23:37 +0100 [thread overview]
Message-ID: <20200211152337.GB8663@nan> (raw)
In-Reply-To: <8876449b-e7ec-3c8f-85d2-962f7940ab72@xs4all.nl>
On Tue, Feb 11, 2020 at 01:07:23PM +0100, Hans Hagen wrote:
> On 2/11/2020 11:56 AM, Rudolf Bahr wrote:
> > On Mon, Feb 10, 2020 at 01:03:38PM +0100, Bahr Rudolf wrote:
> > > On Mon, Feb 10, 2020 at 11:54:49AM +0100, Bahr Rudolf wrote:
> > > >
> > > > Hello ConTeXters!
> > > >
> > > > LuaMetaTeX, Version 2.03.15
> > > > ConTeXt ver: 2020.02.07 18:36 MKIV beta fmt: 2020.2.10
> > > > works well doing my usual tasks.
> > > >
> > > > Now, I put an .otf-font into ".../tex/texmf-local/", and made
> > > > mtxrun --generate
> > > > mtxrun --script fonts --reload
> > > > mtxrun --script fonts --list --all --pattern=<pattern*>,
> > > > but didn't get the expected information on the new font from the last
> > > > command.
> > > >
> > > > So I investigated the output of the first two commands in more detail
> > > > and found:
> > > >
> > > > 1. mtxrun --generate:
> > > > resolvers | resolving | warning: no lua configuration files found
> > > > resolvers | resolving | no texmf paths are defined (using TEXMF)
> > > >
> > > > By the way, "TEXMF" seems to be a mtxrun variable and hasn't directly
> > > > to do with the environmental variable "TEXMF" which gets extinguished.
> > > >
> > > > 2. mtxrun --script fonts --reload:
> > > > mtxrun | the resolver databases are not present or outdated
> > > > mtxrun | unknown script 'fonts.lua' or 'mtx-fonts.lua'
> > > >
> > > >
> > > > Please, what is to be done?
> > > >
> > >
> > >
> > > In context luatex, current version: 2020.01.30 14:13, I'm getting the awaited
> > > information!
> >
> >
> >
> > With
> > LuaMetaTeX, Version 2.03.15
> > ConTeXt ver: 2020.02.10 18:37 MKIV beta fmt: 2020.2.11
> > I'm getting the same results:
> >
> > 1. mtxrun --generate:
> > resolvers | resolving | variable 'TEXMFCNF' set to ''
> > resolvers | resolving | variable 'TEXMF' set to ''
> >
> > resolvers | resolving | warning: no lua configuration files found
> > resolvers | resolving | no texmf paths are defined (using TEXMF)
> >
> > 2. mtxrun --script fonts --reload
> > resolvers | resolving | warning: no lua configuration files found
> > resolvers | resolving | no texmf paths are defined (using TEXMF)
> >
> > mtxrun | the resolver databases are not present or outdated
> > mtxrun | unknown script 'fonts.lua' or 'mtx-fonts.lua'
> >
> >
> > BTW, running "context --make" after wiping "~/context-lmtx/tex/texmf-cache"
> > and running "mtxrun --generate" gives:
> > mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'
> Are you mixing mkiv and lmtx?
> ...
> ...
> so it's either one or the other incarnation of the mtxrun file
Sorry, I don't understand what you mean.
How should it be possible to mix mkiv and lmtx, when I install "LuaMetaTeX 2.03.15"
and "ConTeXt 2020.02.10 MKIV beta" in my linux directory "~/context-lmtx", correct
the PATH variable after installation, do not forget a "source" on ".bashrc" and then
invoke in my directory "context-lmtx" following programs:
mtxrun --generate
mtxrun --script fonts --reload
with the above presented errors?
BTW, if it's important, "~/context-lmtx/tex/texmf-cache/" contains only
"luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e".
Rudolf
___________________________________________________________________________________
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:[~2020-02-11 15:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 10:54 mtxrun Rudolf Bahr
2020-02-10 11:06 ` mtxrun Taco Hoekwater
2020-02-10 11:27 ` mtxrun Rudolf Bahr
2020-02-10 12:03 ` mtxrun Rudolf Bahr
2020-02-11 10:56 ` mtxrun Rudolf Bahr
2020-02-11 12:07 ` mtxrun Hans Hagen
2020-02-11 15:23 ` Rudolf Bahr [this message]
2020-02-11 15:57 ` mtxrun Pablo Rodriguez
2020-02-11 17:26 ` mtxrun Rudolf Bahr
2020-02-11 18:38 ` mtxrun Hans Hagen
2020-02-11 20:41 ` mtxrun Rudolf Bahr
2020-02-11 20:57 ` mtxrun Aditya Mahajan
2020-02-12 5:44 ` mtxrun Rudolf Bahr
2020-02-11 18:39 ` mtxrun Aditya Mahajan
2020-02-12 4:41 ` mtxrun Rudolf Bahr
2020-02-12 5:24 ` mtxrun Aditya Mahajan
2020-02-12 10:05 ` mtxrun Rudolf Bahr
[not found] <mailman.0.1581764401.20240.ntg-context@ntg.nl>
2020-02-15 14:38 ` mtxrun Luca Donetti
2020-02-15 14:48 ` mtxrun Luca Donetti
[not found] <mailman.474.1581455525.1332.ntg-context@ntg.nl>
2020-02-14 19:59 ` mtxrun Luca Donetti
2020-02-15 4:59 ` mtxrun Aditya Mahajan
2020-02-15 5:40 ` mtxrun Rudolf Bahr
2020-02-15 11:32 ` mtxrun Floris van Manen
2020-02-15 14:57 ` mtxrun Aditya Mahajan
-- strict thread matches above, loose matches on Subject: below --
2011-01-23 16:21 MTXrun Herbert Voss
2011-01-23 17:43 ` MTXrun Vedran Miletić
2011-01-23 19:25 ` MTXrun Hans Hagen
2008-06-17 16:49 mtxrun Hans van der Meer
2008-06-17 17:29 ` mtxrun Hans Hagen
2008-06-17 17:34 ` mtxrun Taco Hoekwater
2008-06-17 19:47 ` mtxrun Aditya Mahajan
2008-06-18 8:12 ` mtxrun Hans van der Meer
2008-06-18 9:37 ` mtxrun Hans Hagen
2008-06-18 11:54 ` mtxrun Taco Hoekwater
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=20200211152337.GB8663@nan \
--to=quasi@quasi.de \
--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).