From: Hans Hagen <j.hagen@xs4all.nl>
To: Julian G <juliangmp@pm.me>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to use ConTeXt extensions with VS Code
Date: Tue, 3 Sep 2019 01:50:15 +0200 [thread overview]
Message-ID: <614b6310-ff73-43e8-5aff-542dc80b0ac6@xs4all.nl> (raw)
In-Reply-To: <YKnA4hl_DjG8Wb-ZZ_xqlxKLGaTnXJQLJsO16Ck87WEKi5SlVUpnuFiJCBHiZUz3OHKNAo96qH0VCa7Q83gTrgvvjBR2SITyeKHDqz9K9Ew=@pm.me>
On 9/2/2019 11:18 PM, Julian G wrote:
> 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.
that looks horribly complex and over the top (hard to maintain too)
i prefer just calling the tools (mtxrun etc) as they do most of the work
already (running, checking, helpinfo) but what is currently lacking from
vscode is filetype bound runners (last time i checked) ... i just wait
till that support shows up (i might have missed something recent)
the main reason for me to look into vscode is that it is 'the fashion'
and works ok and is able to support the kind of lexing (syntax
highlighting) that i need (which in turn also determines how my files
look and)
Hans
(who actually uses very little features of editors as he can't remember
all these features anyway so i stick to mastering those that help me most)
-----------------------------------------------------------------
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:50 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
2019-09-02 23:50 ` Hans Hagen [this message]
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=614b6310-ff73-43e8-5aff-542dc80b0ac6@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=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).