mtxrun

older
macro that does not work (Metapost)

Rudolf Bahr

10 Feb 2020 10 Feb '20

3:54 a.m.

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=, 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? Best wishes, Rudolf

Show replies by date

Taco Hoekwater

10 Feb 10 Feb

4:06 a.m.

Hi,

...

On 10 Feb 2020, at 11:54, Rudolf Bahr wrote:

Please, what is to be done?

This usually happens when the mtxrun script you call is not in its ’normal' tree location. It uses its own location to find the rest of its files. For example, one of my context trees has mtxrun in: ~/elvenkind/tex_2014/tex/texmf-osx-64/bin/mtxrun and then it works fine. But If I were to move it to e.g. ~/bin/mtxrun it would (likely) fail to find any files. Best wishes, Taco Taco Hoekwater Elvenkind BV

Rudolf Bahr

4:27 a.m.

On Mon, Feb 10, 2020 at 12:06:43PM +0100, Taco Hoekwater wrote:

...

Hi,

...
On 10 Feb 2020, at 11:54, Rudolf Bahr wrote:

Please, what is to be done?

This usually happens when the mtxrun script you call is not in its ’normal' tree location. It uses its own location to find the rest of its files.

For example, one of my context trees has mtxrun in:

~/elvenkind/tex_2014/tex/texmf-osx-64/bin/mtxrun

and then it works fine. But If I were to move it to e.g.

~/bin/mtxrun

it would (likely) fail to find any files.

Best wishes, Taco

Taco Hoekwater Elvenkind BV

Hi Taco, thank you for your quick answer! I didn't change at all the location of mtxrun. It "resides" in ~/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 These are similar locations as you are using. Best wishes, Rudolf

Rudolf Bahr

5:03 a.m.

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=, 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! Rudolf

Rudolf Bahr

11 Feb 11 Feb

3:56 a.m.

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=, 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' Rudolf

Hans Hagen

5:07 a.m.

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=, 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?

In mkiv: windows: luatex.exe mtxrun.exe (small stub) context.exe (small stub) mtxrun.lua unix: luatex mtxrun (== mtxrun.lua without suffix) context (== mtxrun --script context) In lmtx all platforms have the same approach: windows: luametatex.exe mtxrun.exe (copy of luametatex.exe or link to it) context.exe (copy of luametatex.exe or link to it) mtxrun.lua context.lua unix: luatex mtxrun (copy of luametatex or link to it) context (copy of luametatex or link to it) mtxrun.lua context.lua so it's either one or the other incarnation of the mtxrun file 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 -----------------------------------------------------------------

Rudolf Bahr

8:23 a.m.

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=, 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

Pablo Rodriguez

8:57 a.m.

On 2/11/20 4:23 PM, Rudolf Bahr wrote:

...

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

Hi Rudolf, how did you install ConTeXt? Did you download the proper file from http://pragma-ade.nl/install.htm? What is the output from "whereis mtxrun && whereis context"? Try adding "export PATH=$PATH:~/context/tex/texmf-linux-64/bin/" (correct the path where required) and try again. I’m on Linux64 and I’m not experiencing these issues. And I remove the contents of tex/texmf-cache/ regularly (I only invoke "mtxrun --generate" after that).

...

BTW, if it's important, "~/context-lmtx/tex/texmf-cache/" contains only "luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e".

This is what I have there. These seem to be the standard cache contents. Just in case it helps, Pablo -- http://www.ousia.tk

Rudolf Bahr

10:26 a.m.

On Tue, Feb 11, 2020 at 04:57:15PM +0100, Pablo Rodriguez wrote:

...

On 2/11/20 4:23 PM, Rudolf Bahr wrote:

...
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

Hi Rudolf,

how did you install ConTeXt? Did you download the proper file from http://pragma-ade.nl/install.htm?

What is the output from "whereis mtxrun && whereis context"?

Try adding "export PATH=$PATH:~/context/tex/texmf-linux-64/bin/" (correct the path where required) and try again.

I’m on Linux64 and I’m not experiencing these issues. And I remove the contents of tex/texmf-cache/ regularly (I only invoke "mtxrun --generate" after that).

...
BTW, if it's important, "~/context-lmtx/tex/texmf-cache/" contains only "luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e".

This is what I have there. These seem to be the standard cache contents.

Just in case it helps,

Pablo

Hello Pablo! Thank you for your answer! "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 and "whereis context": ~/context-lmtx/tex/texmf-linux-64/bin/context.lua ~/context-lmtx/tex/texmf-linux-64/bin/context I think, you'll get similar results. These are the informations according to my PATH variable. And in that PATH there are no links to "~/context-luatex", my directory of the other context installation. And as so often I wiped again "texmf-cache": cd ~/context-lmtx/tex/ rm -r texmf-cache/* So, only the empty directory "texmf-cache/" remains. And now: mtxrun --generate gives again the error statements as written earlier. Best wishes, Rudolf

Hans Hagen

11:38 a.m.

...

"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

On 2/11/2020 6:26 PM, Rudolf Bahr wrote: link to the luametatex binary in the texmf-linux-64/bin path 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 -----------------------------------------------------------------

Rudolf Bahr

1:41 p.m.

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

Aditya Mahajan

1:57 p.m.

On Tue, 11 Feb 2020, Rudolf Bahr wrote:

...

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.

This is the wrong binary. As Hans said (and also what I wrote in my message) is that you have to run the one in ~/context-lmtx/tex/texmf-linux-64/bin/

...

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 '..'

I would suggest that you run these commands from outside the ~/context-lmtx directory, so that the above variables show the full path rather than the relative path.

...

"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'

This shows that the wrong binary is being used. You are using the binary in /home/sam/context-lmtx/bin when you should use /home/sam/context-lmtx/tex/texmf-linux-64/bin. Aditya

Rudolf Bahr

10:44 p.m.

On Tue, Feb 11, 2020 at 03:57:27PM -0500, Aditya Mahajan wrote:

...

On Tue, 11 Feb 2020, Rudolf Bahr wrote:

...
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.

This is the wrong binary. As Hans said (and also what I wrote in my message) is that you have to run the one in ~/context-lmtx/tex/texmf-linux-64/bin/

...
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 '..'

I would suggest that you run these commands from outside the ~/context-lmtx directory, so that the above variables show the full path rather than the relative path.

...
"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'

This shows that the wrong binary is being used. You are using the binary in /home/sam/context-lmtx/bin when you should use /home/sam/context-lmtx/tex/texmf-linux-64/bin.

Aditya

Thanks to Hans and Aditya! Using the binaries in /context-lmtx/tex/texmf-linux-64/bin/ instead of ~/context-lmtx/bin/mtxrun brings the awaited result! Remains the question why has it been possible to use the wrong binaries? How could a context user know where the "good" binaries reside? I put the PATH sequence of the official installation process as proposed into my PATH variable and was using "mtxrun". I shall eliminate the error causing context parts in my PATH variable. I'd suggest to correct the proposed completion of PATH variable at the end of the installation process. The knowledge about that has only been possible after a series of mails with Pablo, Hans and Aditya. Thanks again! Rudolf

Aditya Mahajan

11:39 a.m.

On Tue, 11 Feb 2020, Rudolf Bahr wrote:

...

On Tue, Feb 11, 2020 at 04:57:15PM +0100, Pablo Rodriguez wrote:

...
On 2/11/20 4:23 PM, Rudolf Bahr wrote:

...
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

Hi Rudolf,

how did you install ConTeXt? Did you download the proper file from http://pragma-ade.nl/install.htm?

What is the output from "whereis mtxrun && whereis context"?

Try adding "export PATH=$PATH:~/context/tex/texmf-linux-64/bin/" (correct the path where required) and try again.

I’m on Linux64 and I’m not experiencing these issues. And I remove the contents of tex/texmf-cache/ regularly (I only invoke "mtxrun --generate" after that).

...
BTW, if it's important, "~/context-lmtx/tex/texmf-cache/" contains only "luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e".

This is what I have there. These seem to be the standard cache contents.

Just in case it helps,

Pablo

Hello Pablo!

Thank you for your answer!

"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

and "whereis context": ~/context-lmtx/tex/texmf-linux-64/bin/context.lua ~/context-lmtx/tex/texmf-linux-64/bin/context

I think, you'll get similar results. These are the informations according to my PATH variable. And in that PATH there are no links to "~/context-luatex", my directory of the other context installation.

And as so often I wiped again "texmf-cache": cd ~/context-lmtx/tex/ rm -r texmf-cache/* So, only the empty directory "texmf-cache/" remains.

And now: mtxrun --generate gives again the error statements as written earlier.

What is the output of ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate (please paste the complete output; your previous message did not show if SELFAUTOPARENT was being set correctly). Aditya

Rudolf Bahr

9:41 p.m.

On Tue, Feb 11, 2020 at 01:39:54PM -0500, Aditya Mahajan wrote:

...

What is the output of

~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate

(please paste the complete output; your previous message did not show if SELFAUTOPARENT was being set correctly).

Hi Aditya! Thank you for your answer! The output of ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate is big, so I append it here by the file "Aditya-I". It's made by LuaMetaTeX, Version 2.03.15 ConTeXt ver: 2020.02.11 16:41 MKIV beta fmt: 2020.2.11 Just for fun (but perhaps it will help anyway) I append the corresponding output of ~/context-luatex/tex/texmf-linux-64/bin/mtxrun --generate as the file "Aditya-II". This is made by luatex version of context 2020.01.30 14:13 Best wishes, Rudolf

Aditya Mahajan

10:24 p.m.

On Wed, 12 Feb 2020, Rudolf Bahr wrote:

...

On Tue, Feb 11, 2020 at 01:39:54PM -0500, Aditya Mahajan wrote:

...
What is the output of

~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate

(please paste the complete output; your previous message did not show if SELFAUTOPARENT was being set correctly).

Hi Aditya!

Thank you for your answer!

The output of ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate is big, so I append it here by the file "Aditya-I". It's made by LuaMetaTeX, Version 2.03.15 ConTeXt ver: 2020.02.11 16:41 MKIV beta fmt: 2020.2.11

That shows that texmfcnf.lua file was found and resolved. So, `context filename` should work now. Just to be sure, you can try: ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --autogenerate --script context filename where filename is the name of a sample tex file. Aditya

Rudolf Bahr

12 Feb 12 Feb

3:05 a.m.

On Wed, Feb 12, 2020 at 12:24:21AM -0500, Aditya Mahajan wrote:

...

On Wed, 12 Feb 2020, Rudolf Bahr wrote:

...
On Tue, Feb 11, 2020 at 01:39:54PM -0500, Aditya Mahajan wrote:

...
What is the output of

~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate

(please paste the complete output; your previous message did not show if SELFAUTOPARENT was being set correctly).

Hi Aditya!

Thank you for your answer!

The output of ~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --generate is big, so I append it here by the file "Aditya-I". It's made by LuaMetaTeX, Version 2.03.15 ConTeXt ver: 2020.02.11 16:41 MKIV beta fmt: 2020.2.11

That shows that texmfcnf.lua file was found and resolved. So, `context filename` should work now. Just to be sure, you can try:

~/context-lmtx/tex/texmf-linux-64/bin/mtxrun --autogenerate --script context filename

where filename is the name of a sample tex file.

Aditya

Hi Aditya! Thank you for your hint and your help in general! When you wrote before: "This is the wrong binary. As Hans said (and also what I wrote in my message) is that you have to run the one in ~/context-lmtx/tex/texmf-linux-64/bin/", I noticed having misunderstood Hans what he meant with: "i assume that you run the last one in this list, ..." I thought he pointed to my error and didn't understand I should try the last one in the list instead. Anyway, thanks to you, Taco, Pablo and Hans for helping me to solve my problem! Rudolf

1616

Age (days ago)

1618

Last active (days ago)

List overview

Download

16 comments

5 participants

participants (5)

Aditya Mahajan
Hans Hagen
Pablo Rodriguez
Rudolf Bahr
Taco Hoekwater

mtxrun

tags

participants (5)