From: Lars <axteffekt@gmail.com>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Attempt to call a nil value
Date: Sat, 8 Sep 2018 21:06:39 +0200 [thread overview]
Message-ID: <76dd7bbc-7558-0ef5-0c75-b8fe4131bc25@gmail.com> (raw)
In-Reply-To: <40ddb399-3d0e-e496-9244-738bf9df46c9@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2190 bytes --]
Thank you very much Wolfgang. You were a big help, as usual. It never
came to my mind, that the Textadept lexer file /context.lua/ in my
working directory could interfere with /mtxmrun/, which is located
elsewhere. I should also have tried to process files from another
directory instead of trying it from another PC. But since on my tablet
PC I only have one single TeX directory, it didn't come to my mind to
try another one. So again, thank you.
Cheers, Lars.
P. S.: From what I read so far you're a real TeX genius. It's always a
pleasure to write with you.
P. P. S.: Some people really should learn from you, not only when it
comes to TeX.
Am 08/09/2018 um 18:42 schrieb Wolfgang Schuster:
> mtxrun loads the wrong lua file, while it should load mtx-context.lua
> it actually uses context.lua.
>
> Since there is no context.lua in the distribution I guess context.lua
> is one of your files you put in the text directory, remove this file
> (or put it in a different folder) and ConTeXt should work again.
>
> Wolfgang
>
>
> Lars schrieb am 08.09.18 um 18:00:
>>
>> Hello list,
>>
>> since one of the last beta updates (now I have 2018.09.01) I can't
>> use ConTeXt on my Win 10 32bit tablet anymore. I can't make PDFs
>> because I get an error message. In fact, with CTX in my system path
>> of course, even when I type the following into my command prompt, I
>> get the same error:
>>
>> mtxrun --script context
>>
>> ./context.lua:11: attempt to call a nil value (method 'add_rule')
>>
>> This could have to do with the last adaption to Textadept 10. On my
>> Win 10 x64 PC there is no problem. Any clues?
>>
>> Cheers and thanks, Lars.
>>
>>
>>
>> ___________________________________________________________________________________
>> 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
>> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3903 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2018-09-08 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-08 16:00 Lars
2018-09-08 16:42 ` Wolfgang Schuster
2018-09-08 19:06 ` Lars [this message]
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=76dd7bbc-7558-0ef5-0c75-b8fe4131bc25@gmail.com \
--to=axteffekt@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@gmail.com \
/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).