From: Hans Hagen <j.hagen@xs4all.nl>
To: Jeong Dal <haksan@me.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ntg-context Digest, Vol 183, Issue 4
Date: Tue, 3 Sep 2019 01:42:54 +0200 [thread overview]
Message-ID: <fca9e08a-ded1-6a62-23e2-ddc963e769ff@xs4all.nl> (raw)
In-Reply-To: <860129AF-B061-4B40-B9A0-7B10926DCF9D@me.com>
On 9/2/2019 8:48 PM, Jeong Dal wrote:
> Dear Hans,
>
> By adding “setuptex” in the task file, it runs well and makes a pdf output.
>
> {
> "label": "ConTeXt Compile",
> "type": "shell",
> "command": "source ~/ConTeXtLMTX/tex/setuptex;context '${file}'",
in that case, just entering the path to the binary is also an option
> "~/ConTeXtLMTX/tex/texmf-linux-64/bin/mtxrun --autogenerate --script
context --autopdf '${file}'",
> "args": [],
> "group": {
> "kind": "build",
> "isDefault": true
> }
> },
>
> Thank you.
> Best regards,
>
> Dalyoung
>
--
-----------------------------------------------------------------
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-09-02 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1328.1567445713.1208.ntg-context@ntg.nl>
2019-09-02 18:48 ` Jeong Dal
2019-09-02 23:42 ` Hans Hagen [this message]
2019-09-03 12:43 ` :Re: How to use ConTeXt extensions with VS Code Jeong Dal
2019-09-03 22:50 ` Jeong Dal
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=fca9e08a-ded1-6a62-23e2-ddc963e769ff@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=haksan@me.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).