From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use ConTeXt extensions with VS Code
Date: Wed, 28 Aug 2019 09:16:57 +0200 [thread overview]
Message-ID: <6E1230CF-DD48-4DD3-88E9-411A2BF3458F@fiee.net> (raw)
In-Reply-To: <03ef31d5-0baa-0f01-479b-f327d14f7dbf@xs4all.nl>
> Am 2019-08-18 um 22:54 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>
> On 8/18/2019 10:14 PM, Denis Maier wrote:
>> Hi,
>> I have seen ConTeXt comes with an extension for VS Code. How do you use that? I have tried the code in the readme, but this doesn't seem to work.
> there is an vscode-context.cmd file
>
> this could also work:
>
> >mtxrun --script vscode --start
>
> (it's still somewhat experimental and i'm waiting till the editor has better - easier - support for runners associated with suffixes, which currently is kind of one-for-all)
For my ConTeXt editor overview:
Does VScode include a PDF viewer? Does it work with SyncTeX?
Why should one use the mtxrun call?
Does the ConTeXt extension also work with VScodium?
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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-08-28 7:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 20:14 Denis Maier
2019-08-18 20:54 ` Hans Hagen
2019-08-28 7:16 ` Henning Hraban Ramm [this message]
[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
2019-09-02 23:50 ` 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=6E1230CF-DD48-4DD3-88E9-411A2BF3458F@fiee.net \
--to=texml@fiee.net \
--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).