ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rudolf Bahr <quasi@quasi.de>
To: ntg-context@ntg.nl
Subject: Re: mtxrun
Date: Tue, 11 Feb 2020 21:41:14 +0100	[thread overview]
Message-ID: <20200211204114.GA11001@nan> (raw)
In-Reply-To: <cd601582-cfec-dac3-74e1-cd5012533359@xs4all.nl>


On Tue, Feb 11, 2020 at 07:38:54PM +0100, Hans Hagen wrote:
> On 2/11/2020 6:26 PM, Rudolf Bahr wrote:
> 
> > "whereis mtxrun" gives:
> >     ~/context-lmtx/bin/mtxrun.lua
> >     ~/context-lmtx/bin/mtxrun
> >     ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun.lua
> >     ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun
> i assume that you run the last one in this list, which is a copy of or link
> to the luametatex binary in the texmf-linux-64/bin path


Hans, thank you for your answer!

So I run explicitly the second one:
   ~/context-lmtx/bin/mtxrun --generate
but I got the same error.

Now I wiped totally my directory "~/context-lmtx/" and made a new installation
by a newly loaded zip-file from "http://pragma-ade.nl/install.htm" (64 bit Linux),
I canceled the context concerning parts of the PATH variable in .bashrc and took over
the suggested PATH of installation process with a following "source .bashrc" of course:
   LuaMetaTeX, Version 2.03.15
   ConTeXt  ver: 2020.02.11 16:41 MKIV beta  fmt: 2020.2.11

Sorry, "~/context-lmtx/bin/mtxrun --generate" again resulted in:
   resolvers       | resolving | variable 'SELFAUTOLOC' set to 'bin'
   resolvers       | resolving | variable 'SELFAUTODIR' set to '.'
   resolvers       | resolving | variable 'SELFAUTOPARENT' set to '..'
   resolvers       | resolving | variable 'TEXMFCNF' set to ''
   resolvers       | resolving | variable 'TEXMF' set to ''
   resolvers       | resolving | variable 'TEXOS' set to '.'
   ...
   ...
   resolvers       | resolving | warning: no lua configuration files found
   resolvers       | resolving | no texmf paths are defined (using TEXMF)

"mtxrun --generate" run outside the installation directory gets the same result:
   resolvers       | resolving | variable 'SELFAUTOLOC' set to '/home/sam/context-lmtx/bin'
   resolvers       | resolving | variable 'SELFAUTODIR' set to '/home/sam/context-lmtx'
   resolvers       | resolving | variable 'SELFAUTOPARENT' set to '/home/sam'
   resolvers       | resolving | variable 'TEXMFCNF' set to ''
   resolvers       | resolving | variable 'TEXMF' set to ''
   resolvers       | resolving | variable 'TEXOS' set to 'context-lmtx'
   ...
   ...
   resolvers       | resolving | warning: no lua configuration files found
   resolvers       | resolving | no texmf paths are defined (using TEXMF)
   

I assume, as the last line indicates, the error is here: variable 'TEXMF' set to ''.
Am I right in that this variable has nothing to do with an environment variable?

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
___________________________________________________________________________________

  reply	other threads:[~2020-02-11 20:41 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       ` mtxrun Rudolf Bahr
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               ` Rudolf Bahr [this message]
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=20200211204114.GA11001@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).