From: Floris van Manen via ntg-context <ntg-context@ntg.nl>
To: Ramkumar KB <ramkumarkb@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Floris van Manen <vm@klankschap.nl>
Subject: Re: New VSCode extenstion using ConTeXt Language server
Date: Wed, 9 Nov 2022 21:47:26 +0100 [thread overview]
Message-ID: <77ee434d-b9cf-faec-42e7-316075dafa4e@klankschap.nl> (raw)
In-Reply-To: <CAMD5SRNXbnoTXBdd_T1yq2u2L2EMS9wc6cScBVPuVTE+HbD=hA@mail.gmail.com>
On 09/11/2022 14:38, Ramkumar KB wrote:
> Can you please try with VSCode first in Ubuntu and see if this works?
>
> We have never tried with Codium (unfortunately) and therefore not sure
> how the Extension sytem works in Codium.
>
Not too eager to invite the telemetricks into my machine,
so I'll rather opt to wait instead.
No hurry.
.F
___________________________________________________________________________________
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 20:47 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 [this message]
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
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=77ee434d-b9cf-faec-42e7-316075dafa4e@klankschap.nl \
--to=ntg-context@ntg.nl \
--cc=ramkumarkb@gmail.com \
--cc=vm@klankschap.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).