From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Installing VSCode extension?
Date: Wed, 29 Jul 2020 17:12:53 +0200 [thread overview]
Message-ID: <98BF78F2-3133-4A87-A05B-4C229269D0F4@fiee.net> (raw)
In-Reply-To: <CAPGiC77cCggZpO2vj39Sw83Vw-a2pt7DTkGCxmqc+K18vyyw8w@mail.gmail.com>
> Am 29.07.2020 um 14:19 schrieb Alasdair McAndrew <amca01@gmail.com>:
>
> Thank you very much, but in fact that script file "vscode-context.cmd" really just contains the same command for installing extensions as I quoted above - and so produces the same errors. Maybe I'll go back to trying SciTe - I gave it a bit of a go, but wasn't successful. Of all the information on the context-wiki, and the Pragma webpage - where would I go to find the most up-to-date information about configuring an editor to work with ConTeXt in Windows?
You could try Atom and install the ConTeXt module from github.com/massifrg/language-context.
Original language-context is outdated, but upstream didn’t react to mails from Massi and me.
This version also isn’t perfect, but I’m using and occasionally updating it. (I should re-base it on the current work done for the wiki.) There’s also still no run command.
Additionally you should install
- language-latex (contains plain TeX commands)
- language-lua
- atom-ide-terminal (for running ConTeXt in place)
- file-icons (only icon package that contains TeX icons)
- pdf-view (not very good, but good enough for simple cases)
Best, Hraban
___________________________________________________________________________________
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:[~2020-07-29 15:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 4:51 Alasdair McAndrew
2020-07-28 16:50 ` Hans Hagen
2020-07-29 12:19 ` Alasdair McAndrew
2020-07-29 15:12 ` Henning Hraban Ramm [this message]
2020-07-30 1:57 ` Alasdair McAndrew
2020-07-30 6:32 ` Lutz Haseloff
2020-07-30 10:33 ` Henning Hraban Ramm
[not found] <mailman.958.1596074262.23406.ntg-context@ntg.nl>
2020-07-30 5:52 ` Jeong Dal
2020-07-30 10:25 ` Henning Hraban Ramm
2020-08-04 12:38 ` Mikael Sundqvist
2020-12-17 6:28 ` Saša Janiška
2020-12-17 6:51 ` Mikael Sundqvist
2020-12-17 9:40 ` Saša Janiška
2020-12-17 15:55 ` Mikael Sundqvist
[not found] <mailman.1104.1596544715.23406.ntg-context@ntg.nl>
2020-08-05 9:57 ` Jeong Dal
2020-08-05 20:07 ` Mikael Sundqvist
2020-12-02 9:34 ` Saša Janiška
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=98BF78F2-3133-4A87-A05B-4C229269D0F4@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).