ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LMTX issue with multple question blocks
Date: Thu, 7 Nov 2019 18:19:52 +0100	[thread overview]
Message-ID: <463e5798-58ee-6b93-b21b-ce8b20157db1@xs4all.nl> (raw)
In-Reply-To: <64cccf03-c43d-3420-291b-a449476314d7@rik.users.panix.com>

On 11/7/2019 5:36 PM, Rik Kabel wrote:
> On 11/7/2019 11:06, Hans Hagen wrote:
>> On 11/7/2019 3:50 PM, Jan Willem Flamma wrote:
>>> Dear list members,
>>>
>>> The below MWE runs fine and generates a usable PDF.
>>>
>>> If I uncomment the second question block and run the MWE on a OS X 
>>> system it generates an unusable PDF and a nearly empty log file:
>>>
>>> open source     > level 1, order 1, name 'cont-yes.mkiv'
>>> system          >
>>> system          > ConTeXt  ver: 2019.10.28 18:57 MKIV beta  fmt: 
>>> 2019.11.7  int: english/english
>>> system          >
>>> system          > 'cont-new.mkiv' loaded
>>> open source     > level 2, order 2, name 
>>> '/Users/JW/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
>>> system          > beware: some patches loaded from cont-new.mkiv
>>> close source    > level 2, order 2, name 
>>> '/Users/JW/context/tex/texmf-context/tex/context/base/mkiv/cont-new.mkiv'
>>>
>>> system          > files > jobname 'co-intro', input './co-intro', 
>>> result 'co-intro'
>>> fonts           > latin modern fonts are not preloaded
>>> languages       > language 'en' is active
>>> system          > synctex functionality is enabled, expect 5-10 pct 
>>> runtime overhead!
>>> open source     > level 2, order 3, name './co-intro.tex'
>>> fonts           > preloading latin modern fonts (second stage)
>>> fonts           > 'fallback modern-designsize rm 12pt' is loaded
>>> open source     > level 3, order 4, name 'knuth.tex'
>>> close source    > level 3, order 4, name 'knuth.tex'
>>>
>>> I cannot reproduce the problem on a Windows system.
>>>
>>> Can somebody on an OS X system check and confirm the issue?
>> What if you wipe the tuc file?
>>
>> No message?
>>
>> Hans
> 
> I can confirm the same problem on a Win64 problem. I get the same log 
> file (with 2019.10.29 15:09 for the version and my file/directory names).
> 
> There is a console message that is, perhaps, meaningful:
> 
>     This is LuaMetaTeX, Version 2.00.0
>     runtime error : input file 'virtual://block.question.' is not found,
>     quitting
>     mtx-context     | fatal error: return code: 1
in data-vir.lua

local filename = suffix and f_virtual_y(path,n,suffix) or 
f_virtual_n(path,n)

the last n should be suffix, so

local filename = suffix and f_virtual_y(path,n,suffix) or 
f_virtual_n(path,suffix)

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

  reply	other threads:[~2019-11-07 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 14:50 Jan Willem Flamma
2019-11-07 16:06 ` Hans Hagen
2019-11-07 16:36   ` Rik Kabel
2019-11-07 17:19     ` Hans Hagen [this message]
2019-11-07 19:08   ` Jan Willem Flamma
2019-11-07 19:19     ` Wolfgang Schuster
2019-11-08  9:09       ` Jan Willem Flamma

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=463e5798-58ee-6b93-b21b-ce8b20157db1@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --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).