From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: another error message in LMTX
Date: Sat, 7 Nov 2020 12:41:43 +0100 [thread overview]
Message-ID: <f648b320-ff67-da50-d3b5-a1b2dcfdf9f6@gmx.es> (raw)
Hans,
using latest from yesterday, I get the following error:
tex error > tex error on line 22 in file cont-yes.mkiv: Valid
keyword expected, likely 'minus'
<lua output> mt
xrunjit
<to be read again>
\relax
<macro> \buff_verbatim_type_buffer_indeed ...rrentregime
}tab{\typingparameter \c!tab }method{\p_buff_option
}escape{\typingparameter \c!escape }nature{display}\relax
\dostoptagged \endofverbatimlines \dostoptagged \stoppacked
\typingparameter \c!after
[...]
You started a keyword but it seems to be an invalid one. The first
character(s) might give you a clue. You might want to quit unwanted
lookahead with \relax.
This comes from a book with > 300pp. It compiles perfectly fine with
MkIV, so the typo might be in LMTX itself.
I wonder whether it would be possible to add the invalid keyword (and
related command) to the error message. This would mean something like:
tex error > tex error on line 22 in file cont-yes.mkiv: Valid
keyword expected, got "invalid one" (related to "command").
This would help a lot to figure out where to start searching for clues
for a MWE.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 reply other threads:[~2020-11-07 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 11:41 Pablo Rodriguez [this message]
2020-11-07 12:29 ` Hans Hagen
2020-11-07 14:31 ` Pablo Rodriguez
2020-11-07 14:51 ` Hans Hagen
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=f648b320-ff67-da50-d3b5-a1b2dcfdf9f6@gmx.es \
--to=oinos@gmx.es \
--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).