ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: Hans Hagen <j.hagen@xs4all.nl>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Which version of MkIV should we use?
Date: Mon, 26 Oct 2020 08:05:15 -0400	[thread overview]
Message-ID: <659f37d4-c130-4ea3-843d-a8df45d272ab@rik.users.panix.com> (raw)
In-Reply-To: <4193ed55-5343-c49a-b6ec-1ded8fbb3310@xs4all.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2963 bytes --]

On 10/26/2020 04:37, Hans Hagen wrote:
> On 10/26/2020 12:09 AM, Rik Kabel wrote:
>> Hello all,
>>
>> I have noticed some differences between the MkIV installed as part of 
>> LMTX and the MkIV installed via first-setup.
>>
>> Which should be used going forward when one wants to use MkIV?
>>
>> (One difference: \contextkind is defined in file context.mkiv 
>> installed via first-setup. It is not defined in the file of the same 
>> name installed as part of LMTX. Another, more significant difference, 
>> is loading modules.)
>
> mkiv works with luatex, lmtx needs luametatex
>
> currently the functionality is mostly the same but further development 
> happens in lmtx
>
> so, if mkiv works for you, just keep using it .. you can try your 
> document with lmtx and normally that should work ok
>
> there is a distinction between
>
> - core functionality (seldom changes)
> - tricky things (migh tbe done better in lmtx)
> - more radical new things hard to do in regular tex (will be in lmtx 
> only)
>
> the luametatex engine is more advanced than luatex (which we cannot 
> change any more in fundamental ways as it's also used outside context) 
> but with luametatex we can do (maybe) crazy things; the luametatex 
> enfine has all kind of improvements in the rendening, adds 
> functionality that makes implementations somewhat cleaner, is faster 
> and uses less memory, redesigns/organizes some internals (e.g. get rid 
> of the sometimes fuzzy accumulated engine mix), adds more interfaces 
> in lua, is self contained, etc ... see presentation(s) last ctx meeting.
>
> currently i'm applying some of the more drastic new thing: more 
> advance macro argument parsing options, several levels of (macro) 
> protection, etc which actually might lead to issues (simple to deal 
> with as most are interface related, not functionality)
>
> so ... you can use mkiv and/or snapshot the current lmtx and/or try 
> the latest greatest when it showsup
>
> 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
> -----------------------------------------------------------------

Hans,

Let me rephrase the question.

With the following example:

    \starttext

    \contextkind

    \stoptext

The standalone installation returns a document containing "beta" and 
context --luatex with the LMTX installation complains of an undefined 
control sequence.

The file context.mkiv differs between the two installations.

If the two are expected to differ, I am asking which is the reliable 
version.

You had stated in an earlier email that the --luatex option provided to 
an LMTX installation will produce an MkIV result, but that does not seem 
to still be the case.

-- 
Rik


[-- Attachment #1.2: Type: text/html, Size: 4141 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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
___________________________________________________________________________________

  reply	other threads:[~2020-10-26 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 23:09 Rik Kabel
2020-10-26  8:37 ` Hans Hagen
2020-10-26 12:05   ` Rik Kabel [this message]
2020-10-28 13:49     ` Rik Kabel

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=659f37d4-c130-4ea3-843d-a8df45d272ab@rik.users.panix.com \
    --to=context@rik.users.panix.com \
    --cc=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).