From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: follow up
Date: Fri, 5 Apr 2019 00:28:19 +0200 [thread overview]
Message-ID: <8f908232-5516-b2a7-df76-51eba0c5140e@xs4all.nl> (raw)
In-Reply-To: <0CE7B8A0-C74F-45F4-86C4-C5DAD8DA994E@me.com>
On 4/5/2019 12:17 AM, Jeong Dal wrote:
> Dear Hans,
>
> I have installed both ConTeXt LMTX and ConTeXt MKIV side by side.
> But I have a problem to run it.
>
> If it is OK to run a file in LMTX environment, then I got a following
> error when I run it in MKIV environment.
> “I can’t fine a file …../defFonts.tex” even though it is there.
> To resolve it, I run “mtxrun —generate” in MKIV.
> But it invoke the same type error in LMTX.
> Here are the command in Atom editor which I use to run it.
>
> LMTX:
> source /Users/graph/ConTeXtLMTX/tex/setuptex;
> context {filePath}
> MKIV:
> source /Users/graph/ConTeXt/tex/setuptex;
> context {filePath}
>
> I may avoid it by adding “mtxrun —generate” before compiling it.
> But it isn’t a good solution.
> I think that there is a better way to do this.
> Would you please tell me how to fix it or what is a better way?
Does
<path to>/mtxrun --autogenerate --script context --autopdf {filePath}
work in your editor?
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-04-04 22:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.557.1554137032.1194.ntg-context@ntg.nl>
2019-04-02 11:49 ` Jeong Dal
2019-04-02 12:25 ` Hans Hagen
2019-04-02 12:40 ` Floris van Manen
2019-04-02 12:50 ` Hans Hagen
2019-04-02 13:12 ` Floris van Manen
2019-04-02 13:23 ` Hans Hagen
2019-04-02 13:58 ` Floris van Manen
2019-04-02 14:18 ` Ulrike Fischer
2019-04-02 14:50 ` Hans Hagen
2019-04-02 15:11 ` Hans Hagen
2019-04-02 18:38 ` Taco Hoekwater
2019-04-02 19:29 ` Floris van Manen
2019-04-02 20:16 ` Hans Hagen
2019-04-03 5:58 ` Christoph Reller
2019-04-03 7:06 ` Hans Hagen
2019-04-02 14:42 ` Hans Hagen
2019-04-04 22:17 ` Jeong Dal
2019-04-04 22:28 ` Hans Hagen [this message]
2019-04-05 6:49 ` Otared Kavian
[not found] <mailman.769.1554712325.1194.ntg-context@ntg.nl>
2019-04-08 13:32 ` Jeong Dal
[not found] <mailman.1.1554458401.26589.ntg-context@ntg.nl>
2019-04-05 14:30 ` Jeong Dal
2019-04-08 8:32 ` Otared Kavian
2019-04-01 12:56 Hans Hagen
2019-04-01 13:18 ` Floris van Manen
2019-04-01 13:31 ` Mojca Miklavec
2019-04-01 19:41 ` Henning Hraban Ramm
2019-04-02 15:56 ` Aditya Mahajan
2019-04-02 16:24 ` 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=8f908232-5516-b2a7-df76-51eba0c5140e@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).