From: Otared Kavian <otared@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: "error not related to input file"
Date: Sat, 14 Dec 2019 19:27:34 +0100 [thread overview]
Message-ID: <71687971-6775-47E7-A0C5-6E81F5643D31@gmail.com> (raw)
In-Reply-To: <20191214165746.GA5618@nan>
Hi,
Since I have also suffered somewhat from the cryptic (and often useless…) error messages, I understand your frustration :-)
Now, maybe if you do
context --directives="system.showerror" myfile.tex
then you get a file named « myfile-status.html » which is more helpful.
Best regards: OK
> On 14 Dec 2019, at 17:57, Rudolf Bahr <quasi@quasi.de> wrote:
>
>
> On Sat, Dec 14, 2019 at 05:43:45PM +0100, Bahr Rudolf wrote:
>>
>> Hello All,
>>
>> In:
>> LuaMetaTeX, Version 2.03.3
>> ConTeXt ver: 2019.12.12 19:35 MKIV beta fmt: 2019.12.12 int: english/english
>> I get the following error message:
>>
>> tex error > error not related to input file:
>> tex error > tex: ! Emergency stop
>> tex error > lua: ?
>> tex error > mps: -
>>
>> Sorry, no MWE available.
>> What does this message mean? [1] shows only an empty page.
>> To this point my programm does all what it should with the exception of creating
>> a grey pdf-file-page. My pdf-programs are okular and xpdf.
>>
>> In:
>> LuaTeX, Version 1.11.2 (TeX Live 2020/dev)
>> ConTeXt ver: 2019.12.12 19:23 MKIV beta fmt: 2019.12.13 int: english/english
>> I get a "*" instead of the error message above. And again my program does all what
>> it should, but a grey pdf-page too.
>>
>> Shure, there must be an error in my program. But where should I look for it?
>> I tried several MWEs, but they all worked at their best.
>>
>> Please, any ideas?
>>
>> Best wishes,
>> Rudolf
>>
>>
>> [1] https://wiki.contextgarden.net/error_not_related_to_input_file
>>
>
>
> Sorry, I forgot:
> My program uses up to now mainly \startluacode ... \stopluacode.
>
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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:[~2019-12-14 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 16:43 Rudolf Bahr
2019-12-14 16:57 ` Rudolf Bahr
2019-12-14 18:27 ` Otared Kavian [this message]
2019-12-14 21:31 ` Hans Hagen
2019-12-16 20:03 ` Rudolf Bahr
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=71687971-6775-47E7-A0C5-6E81F5643D31@gmail.com \
--to=otared@gmail.com \
--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).