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>,
	Otared Kavian <otared@gmail.com>,
	Adam Reviczky <reviczky@gmail.com>
Subject: Re: How can I use ConTeXt from TeXLive2020 ?
Date: Tue, 11 Aug 2020 17:25:53 +0200	[thread overview]
Message-ID: <2fd60bbe-a9bc-3497-6b15-ae50c2d0e903@xs4all.nl> (raw)
In-Reply-To: <3FD5958C-CF56-4F58-855C-C86D9C16DADD@gmail.com>

Hi,

A few remarks.

In a mkiv luatex setup there are (on a unix system):

   luatex  : binary
   mtxrun  : a copy of mtxrun.lua
   context : a shell script starting mtxrun

Now, the problem there is that these shebang lines are limited, i.e. 
there is no way to pass an argument and we need to start luatex in lua 
mode. This is why the program refered to is texlua which is a copy of or 
symlink to luatex and when called with that name it knows that it has to 
start in lua mode.

On windows there are two small stubs: mtxrun.exe and context.exe an both 
will start luatex (no need for texlua there) with the same script etc.

In a luametatex setup we have a uniform and simpler model.

   luametatex   : binary
   mtxrun       : a copy of luametex or symlink to it
   context      : a copy of luametex or symlink to it
   mtxrun.lua   : used when mtxrun is started
   context.lua  : used when context is started

So, here the 'context' link (or copy) from it's name knows to start in 
lua mode and load context.lua (which actually loads mtxrun.lua + 
mtx-context.lua). It's the same on all platforms.

Now, already long ago we ditched all other stubs simply because given 
the amount of scripts in a tex live setup it's a recipe for clashes 
(scripts also have to compete with programs / scripts  installed as part 
of the os and other programs so even more opportunity for clashes). We 
just use

   mtxrun --script ...

instead (and texmfstart in a mkii setup).

These models cannot be mixed, which is why in a luametatex lmtx setup we 
use "context --luatex" to start mkiv, where luametatex is the runner.

Hans

ps. I remember the times that context was considered bad because it 
needed a runner, read: a script was part of the deal and a tex run 
should not have such a depedency; the need to install perl or ruby was 
seen as a shortcoming. We also used scripts to generate font metric 
files (context didn't depend on other programs for toc and index 
generation and had just one auxiliary file). But times have changed and 
scripts are now hip and modern in the tex ecosysystem, which is why we 
basically limit ourselves to just 'context' and 'mtxrun' and start all 
the other context related scripts indirectly.

-----------------------------------------------------------------
                                           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:[~2020-08-11 15:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10 10:03 Otared Kavian
2020-08-10 10:37 ` Taco Hoekwater
2020-08-10 10:39 ` Axel Kielhorn
2020-08-10 12:59   ` Otared Kavian
2020-08-10 13:07     ` Taco Hoekwater
2020-08-10 13:20     ` Hans Hagen
2020-08-10 14:08       ` Otared Kavian
2020-08-10 14:15       ` Axel Kielhorn
2020-08-10 14:11     ` Axel Kielhorn
2020-08-10 22:02       ` Otared Kavian
     [not found]         ` <CABaoHuseyOm++oDmxjmJteZHXjA+JnV8+yEwb1rnzZWEC=c09w@mail.gmail.com>
2020-08-11 14:57           ` Otared Kavian
2020-08-11 15:25             ` Hans Hagen [this message]
2020-08-11 20:38               ` Otared Kavian
2020-08-12  6:26             ` Axel Kielhorn
2020-08-13  9:04               ` Otared Kavian
2020-08-13 10:42                 ` Axel Kielhorn
2020-08-13 14:57                 ` Mojca Miklavec
2020-08-14  7:43                   ` Otared Kavian
2020-08-14  9:42                     ` Mojca Miklavec

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=2fd60bbe-a9bc-3497-6b15-ae50c2d0e903@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=otared@gmail.com \
    --cc=reviczky@gmail.com \
    /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).