ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Cannot build plain format
Date: Fri, 17 Apr 2020 11:51:15 +1200	[thread overview]
Message-ID: <20200416235115.fodf5e3e6jgxhe4g@worklaptop> (raw)
In-Reply-To: <98c7bdfb-555e-2ee6-06cc-e4fee64528e5@xs4all.nl>

On 16/04/20, 12:35, Hans Hagen wrote:
> On 4/16/2020 10:51 AM, Henri Menke wrote:
> > Dear list,
> > 
> > I'm trying to build the plain format but it fails with
> > 
> >      $ mtxrun --script plain --make
> >      [...]
> >      ! I can't find file `luatex-plain.tex'.
> > 
> > but mtxrun can find the file.
> > 
> >      $ mtxrun --find-file "luatex-plain.tex"
> >      /opt/context/tex/texmf-context/tex/generic/context/luatex/luatex-plain.tex
> > 
> > What am I doing wrong?
> > 
> > Also another question: Does LMTX come with a plain format?
> 
> currently not but as i for now also have added luatex to it (as it's handy
> for testing) i can also add plain related files (these depend on luatex)

Thanks, but what about the first part of my email?  Why can't I build
the plain format in ConTeXt standalone (MkIV, not LMTX) even though
mtxrun can locate the file?

Cheers, Henri

> 
> Hans
> 
> (fwiw: I only use plain for an occasional test of the shipped generic font
> loader files.)
> 
> 
> -----------------------------------------------------------------
>                                           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
> ___________________________________________________________________________________
___________________________________________________________________________________
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-04-16 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16  8:51 Henri Menke
2020-04-16 10:35 ` Hans Hagen
2020-04-16 23:51   ` Henri Menke [this message]
2020-04-19  9:57     ` Hans Hagen
2020-04-19 10:44       ` New installation setup (was: Cannot build plain format) Henning Hraban Ramm
2020-04-19 13:39         ` New installation setup 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=20200416235115.fodf5e3e6jgxhe4g@worklaptop \
    --to=henrimenke@gmail.com \
    --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).