From: Alan Braslau <braslau.list@comcast.net>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Saša Janiška" <gour@atmarama.com>
Subject: Re: LSP support
Date: Sat, 27 Jun 2020 10:14:49 -0600 [thread overview]
Message-ID: <1d8f46dc-97ae-829c-a181-167c8734d03c@comcast.net> (raw)
In-Reply-To: <20200627121302.244efc9d@atmarama.ddns.net>
A start:
lua-lsp
A Language Server for Lua code, written in Lua.
Supports Lua 5.1-5.3 and Luajit
Alan
On 27/06/20 04:13, Saša Janiška wrote:
> Hello,
>
> yesterday while exploring features/plugins of Kakoune (https://kakoune.org/)
> editor I, naturally, asked about ConTeXt/LaTeX support and was told about
> TexLab project (https://github.com/latex-lsp/texlab) bringing LSP
> (https://microsoft.github.io/language-server-protocol/) support for LaTeX.
> Interestingly enough, by browsing through the tickets I've found the following
> issue: "ConTeXt support" (https://github.com/latex-lsp/texlab/issues/166) where
> one of the, afaict, main devs of the project replied with:
>
> "ConTeXt support is definitely in scope of this project.
> Our LaTeX parser does not rely on LaTeX specifics
> but a lot of the features like code completion rely on LaTeX specifics.
> Nevertheless, supporting ConTeXt is a lot of effort at the moment
> as I have never used ConTeXt before.
> Supporting the project structure of ConTeXt would probably be the first
> step. "
>
> 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.
>
> 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.
>
>
> Sincerely,
> Saša
>
___________________________________________________________________________________
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-06-27 16:14 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 [this message]
2020-06-28 11:36 ` TeXnician
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=1d8f46dc-97ae-829c-a181-167c8734d03c@comcast.net \
--to=braslau.list@comcast.net \
--cc=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).