From: Jeong Dal <haksan@me.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use ConTeXt extensions with VS Code
Date: Tue, 3 Sep 2019 02:35:05 +0900 [thread overview]
Message-ID: <E6AAB97E-2F19-4889-8237-30622AC31793@me.com> (raw)
In-Reply-To: <bd3e216e-f09f-aa2f-977b-60ac838e4858@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1102 bytes --]
Dear Hans,
>> But I cannot see any syntax coloring and don’t know how to compile a TeX file.
>> Would you please help me more?
> I think you also need to choose the context color scheme
>
Yes, syntax coloring works after choosing the context color scheme.
I find a following task file to compile a file from vscode, but it doesn’t work.
Here is the error message:
/bin/bash: context: command not found
The terminal process terminated with exit code: 127
%%%%%
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "ConTeXt build",
"type": "shell",
// Keep in mind that the file path here has to be changed
"command": "context myfile.tex",
"group": {
"kind": "build",
"isDefault": true
// Since we set this task to the default build task, you can
// run it with a keyboard shortcut (Ctrl+Shift+B by default)
}
}
]
}
%%%%%%%
i am using ConTeXtLMTX installed ~/ConTeXtLMTX/.
Thank you.
Best regards,
Dalyoung
[-- Attachment #1.2: Type: text/html, Size: 26499 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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-09-02 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.915.1566199312.1208.ntg-context@ntg.nl>
2019-09-02 5:33 ` Jeong Dal
2019-09-02 6:47 ` Hans Hagen
2019-09-02 13:24 ` Jeong Dal
2019-09-02 13:44 ` Hans Hagen
2019-09-02 17:35 ` Jeong Dal [this message]
2019-09-02 18:47 ` Hans Hagen
2019-09-02 21:18 ` Julian G
2019-09-02 23:50 ` Hans Hagen
2019-08-18 20:14 Denis Maier
2019-08-18 20:54 ` Hans Hagen
2019-08-28 7:16 ` Henning Hraban Ramm
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=E6AAB97E-2F19-4889-8237-30622AC31793@me.com \
--to=haksan@me.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).