From: "Saša Janiška via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: "Saša Janiška" <sjaniska@atmarama.net>
Subject: Re: New VSCode extenstion using ConTeXt Language server
Date: Wed, 9 Nov 2022 14:59:49 +0100 [thread overview]
Message-ID: <20221109145949.10e5e028@atmarama.ddns.net> (raw)
In-Reply-To: <CAMD5SRNWm0n2GmZFpSTMv0Yt3FouurLi=OXJPs9o6ezp3m=6aQ@mail.gmail.com>
On Tue, 8 Nov 2022 22:20:10 +0800
Ramkumar KB via ntg-context <ntg-context@ntg.nl> wrote:
> Hello All,
>
> I have published the new VSCode Extension for ConTeXt, that I
> presented during the 2022 ConTeXt meeting -
>
> https://wiki.contextgarden.net/VSCode
Any plan to make it work with other editors which do support LSP?
Sincerely,
Saša
--
In this endeavor there is no loss or diminution,
and a little advancement on this path can protect
one from the most dangerous type of fear.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-11-09 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 14:20 Ramkumar KB via ntg-context
2022-11-08 15:41 ` New VSCode extension " Henning Hraban Ramm via ntg-context
2022-11-08 15:55 ` New VSCode extenstion " Floris van Manen via ntg-context
2022-11-09 13:38 ` Ramkumar KB via ntg-context
2022-11-09 20:47 ` Floris van Manen via ntg-context
2022-11-09 12:36 ` Denis Maier via ntg-context
2022-11-09 13:47 ` Ramkumar KB via ntg-context
2022-11-09 13:59 ` Saša Janiška via ntg-context [this message]
2022-11-09 14:02 ` Saša Janiška via ntg-context
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=20221109145949.10e5e028@atmarama.ddns.net \
--to=ntg-context@ntg.nl \
--cc=sjaniska@atmarama.net \
/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).