From: Mikael Sundqvist <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Installing VSCode extension?
Date: Tue, 4 Aug 2020 14:38:05 +0200 [thread overview]
Message-ID: <CAHy-LL_ew1Jv6wOesX7PzP+vbjmEAmqTpm4+y4Tj2oXr1-L6WA@mail.gmail.com> (raw)
In-Reply-To: <4ECE59FD-6C48-4B38-BEA3-68EE3D0441B6@fiee.net>
[-- Attachment #1.1: Type: text/plain, Size: 2186 bytes --]
On Thu, Jul 30, 2020 at 12:25 PM Henning Hraban Ramm <texml@fiee.net> wrote:
>
> > Am 30.07.2020 um 07:52 schrieb Jeong Dal <haksan@me.com>:
> >
> > Dear Alasdair McAndrew,
> >
> > I am using vscode in iMac, so my setting may not work for you.
> >
> >
> >
> > 1. First, find files for vscode in your TeX folder.
> >
> > In my case,
> >
> >
> /ConTeXt-homefolder/tex/texmf-context/context/data/vacode/extensions/context/*.*
> >
> > 2. In a homefolder, there is a hidden folder “.vacode”.
> >
> > Copy context/*.* to ./vscode/extensions/context/*.*
> >
> > 3. Open vscode and enable context-extension.
> >
> > Since it was long time ago, my memory may not be correct.
> > However, I hope that it may give you an idea.
>
> It might make sense to not copy the files but symlink the folder (then it
> automatically receives updates).
> i.e.
> ln -s $TEXROOT/texmf-context/context/data/vacode/extensions/context
> ~/.vscode/extensions/
>
> Don’t know how symlinking in Windows works, though.
>
> HR
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
Hi!
To make a symlink worked well here, in the sense that I got a context
extension in vs code, and when opening a context file it was recognized as
such. I could go into the extension settings and enable color syntax.
Questions:
1) Is there a way to get autocompletion on all context commands (not only
the ones I have in the document)? If so, how?
2) Is there a nice way to compile the tex file from within vs code? As of
now, I opened a terminal and compiled from that, but that feels like the
wrong way of doing it.
I'm on linux and with the latest standalone (lmtx if that matters).
/Mikael
[-- Attachment #1.2: Type: text/html, Size: 3246 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 prev parent reply other threads:[~2020-08-04 12:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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
2020-07-30 1:57 ` Alasdair McAndrew
2020-07-30 6:32 ` Lutz Haseloff
2020-07-30 10:33 ` 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=CAHy-LL_ew1Jv6wOesX7PzP+vbjmEAmqTpm4+y4Tj2oXr1-L6WA@mail.gmail.com \
--to=mickep@gmail.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).