From: TeXnician <texnician@e.mail.de>
To: ntg-context@ntg.nl
Subject: Re: LSP support
Date: Sun, 28 Jun 2020 13:36:29 +0200 [thread overview]
Message-ID: <291725d9-8843-1913-5b44-a3e268f68cef@e.mail.de> (raw)
In-Reply-To: <20200627121302.244efc9d@atmarama.ddns.net>
> Of course, I'm glad that TexLab project does provide LSP support and bringing
> it to the Kakoune editor as well, but I'm sure that many of you know
> that bringing ConTeXt support to TexLab would benefit users of **many**
> other editors since these today many most popular editors (Atom, Emacs,
> SublimeText, (neo)Vimn, VScode...) are having support for LSP.
TeXLab is not the only LSP for *TeX.
https://github.com/astoff/digestif merged ConTeXt support including some TikZ
wrapping for ConTeXt etc. (Have a look at PR #24.)
It is written in Lua, so if you feel more native there you could contribute.
> Unfortuantely, I'm ConTeXt noob and not speaking Rust, but just want to bring
> the information if there are people familiar with both about potential benefit
> for ConTeXt to get LSP support.
If someone would extend TeXLab that would surely benefit many. But they seem
much more hard-wired towards LaTeX.
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-06-28 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 10:13 Saša Janiška
2020-06-27 16:14 ` Alan Braslau
2020-06-28 11:36 ` TeXnician [this message]
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=291725d9-8843-1913-5b44-a3e268f68cef@e.mail.de \
--to=texnician@e.mail.de \
--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).