From: Jeong Dal <haksan@me.com>
To: "list ntg-context@ntg.nl ntg-context@ntg.nl ntg-context@ntg.nl
ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: How to use ConTeXt extensions with VS Code
Date: Mon, 2 Sep 2019 14:33:11 +0900 [thread overview]
Message-ID: <8FABE251-E7E2-4499-9AE4-AED4A830C5E4@me.com> (raw)
In-Reply-To: <mailman.915.1566199312.1208.ntg-context@ntg.nl>
[-- Attachment #1.1: Type: text/plain, Size: 328 bytes --]
Dear Hans,
> 2019. 8. 19. 오후 4:21, ntg-context-request@ntg.nl 작성:
>
> there is an vscode-context.cmd file
>
Where can I find a vscode-context.cmd file?
I couldn’t locate it using google search.
> this could also work:
>
>> mtxrun --script vscode --start
>
Thank you.
Best regards,
Dalyoung
[-- Attachment #1.2: Type: text/html, Size: 3605 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 parent reply other threads:[~2019-09-02 5:33 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 [this message]
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
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=8FABE251-E7E2-4499-9AE4-AED4A830C5E4@me.com \
--to=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).