From: "Saša Janiška" <gour@atmarama.com>
To: ntg-context@ntg.nl
Subject: Re: Installing VSCode extension?
Date: Thu, 17 Dec 2020 07:28:43 +0100 [thread overview]
Message-ID: <20201217072843.0668b618@atmarama.ddns.net> (raw)
In-Reply-To: <CAHy-LL_ew1Jv6wOesX7PzP+vbjmEAmqTpm4+y4Tj2oXr1-L6WA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
On Tue, 4 Aug 2020 14:38:05 +0200
Mikael Sundqvist <mickep@gmail.com> wrote:
> 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 was able to install vscode extension by symlinking...
> I could go into the extension settings and enable
> color syntax. Questions:
How to do that?
I do not see such setting - see attached screenshot.
> 1) Is there a way to get autocompletion on all context commands (not
> only the ones I have in the document)? If so, how?
I've the same question?
> I'm on linux and with the latest standalone (lmtx if that matters).
Same here.
I also wonder about snippets, are there some?
To write markdown, I can get great support with *any* editor - Emacs,
Vim, Oni2, ST3(4) and same is true for PHP/HTML/CSS coding which I plan
to do, but ConTeXt support and LSP features are not so great in
comparison while I'd not like being forced to change (ConTeXt) markup
due to editor-related issues.
Anyone?
Sincerely,
Gour
--
Even the intelligent are bewildered in determining what is action
and what is inaction. Now I shall explain to you what action is,
knowing which you shall be liberated from all misfortune.
[-- Attachment #2: vscode-extension.jpg --]
[-- Type: image/jpeg, Size: 34513 bytes --]
[-- Attachment #3: 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-12-17 6:28 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
2020-12-17 6:28 ` Saša Janiška [this message]
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=20201217072843.0668b618@atmarama.ddns.net \
--to=gour@atmarama.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).