From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: issues with current latest
Date: Fri, 14 Oct 2022 16:24:03 +0200 [thread overview]
Message-ID: <da879faf-1c80-5ecb-0720-330d61e5de9c@gmx.es> (raw)
Dear list,
I have the following sample:
\setuppapersize[A7]
\setupinteraction[state=start,
color=darkred,
contrastcolor=darkred,
focus=standard]
\starttext
\completecontent
\startsection[title={sec}, list=(before \&\ now), reference=a]
\page
\in[a] (after 2022.10.14 10:16)
\stopsection
\stoptext
If I try to compile with LuaTeX (after deleting the cache), I get the
following error:
lua error > lua error on line 1 in file a.tex:
...tex/texmf-context/tex/context/fonts/mkiv/common-math.lfg:100: attempt
to index a nil value (field 'subsets')
stack traceback:
...tex/texmf-context/tex/context/fonts/mkiv/common-math.lfg:100: in
field 'moveitalics'
.../context/tex/texmf-context/tex/context/fonts/mkiv/lm.lfg:103: in
main chunk
[C]: in function 'dofile'
...ext/tex/texmf-context/tex/context/base/mkiv/good-ini.lua:78: in
function <...ext/tex/texmf-context/tex/context/base/mkiv/good-ini.lua:68>
(...tail calls...)
It is also caused by the minimal:
\starttext
\null
\stoptext
And with the first source, \in hyperlink doesn’t work at all.
Sylvain reported an issue with the \completecontent list (not honoring
"focus=standard"), but with current latest the \in hyperlink doesn’t
work at all.
Could anyone confirm the issues?
Many thanks for your help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2022-10-14 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 14:24 Pablo Rodriguez via ntg-context [this message]
2022-10-14 14:34 ` Alain Delmotte via ntg-context
2022-10-14 20:24 ` Pablo Rodriguez via ntg-context
2022-10-14 21:38 ` Max Chernoff via ntg-context
2022-10-14 22:20 ` Alan Braslau via ntg-context
2022-10-14 22:33 ` Max Chernoff via ntg-context
2022-10-14 22:38 ` Alan Braslau via ntg-context
2022-10-14 22:46 ` Max Chernoff via ntg-context
2022-10-15 7:34 ` Hans Hagen via ntg-context
2022-10-15 7:35 ` Hans Hagen via ntg-context
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=da879faf-1c80-5ecb-0720-330d61e5de9c@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).