From: Julian G <juliangmp@pm.me>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use ConTeXt extensions with VS Code
Date: Mon, 02 Sep 2019 21:18:34 +0000 [thread overview]
Message-ID: <YKnA4hl_DjG8Wb-ZZ_xqlxKLGaTnXJQLJsO16Ck87WEKi5SlVUpnuFiJCBHiZUz3OHKNAo96qH0VCa7Q83gTrgvvjBR2SITyeKHDqz9K9Ew=@pm.me> (raw)
In-Reply-To: <017fa7ad-8f7e-cd5b-89a0-03368a55185d@xs4all.nl>
On Monday, 2 September 2019 20:47, Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 9/2/2019 7:35 PM, Jeong Dal wrote:
>
> > 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=
> > http://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/.
>
> you probably need to set the path before you start the 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
Hello,
I tried searching for that file but didn't find it, there's also no "vscode" script listed when running "mtxrun --script"
I installed using texlive on windows, is the script only shipped on the standalone installation?
If it's possible to create a fully fledged ConTeXt extension for vscode with these files, I would try to create it. I'm not that experienced with javascript, but I think I should be able to get some stuff done. You could also utlize some code from the existing LaTeX workshop extension ( https://github.com/James-Yu/LaTeX-Workshop ), since it features a pdf preview with working synctex.
Best regards,
Julian
___________________________________________________________________________________
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 21:18 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
2019-09-02 18:47 ` Hans Hagen
2019-09-02 21:18 ` Julian G [this message]
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='YKnA4hl_DjG8Wb-ZZ_xqlxKLGaTnXJQLJsO16Ck87WEKi5SlVUpnuFiJCBHiZUz3OHKNAo96qH0VCa7Q83gTrgvvjBR2SITyeKHDqz9K9Ew=@pm.me' \
--to=juliangmp@pm.me \
--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).