Re: AsciiDoctor & LSP support

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor & LSP support

mojavelinux
Administrator
> it would greatly benefit markup language since all the major editors have LSP clients

I definitely recognize the need and benefit of having an LSP impl, but we also must be honest. Not all major editors use it. This is really about satisfying a need of VSCode and I suppose Sublime too. The IntelliJ plugin does not use LSP and is quite successful without it. But I'll let Alexander comment on whether an LSP impl would be more ideal.

-Dan

On Thu, Dec 17, 2020 at 6:21 AM gour [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Hello,

since there is better support for editor(s) I want to use (e.g. SublimeText) for AsciiDoc(tor) than for the ConTeXt markup, I've decided to use it for all my writings (blog posts, slide-presentations, study-notes, articles etc.), but I wonder if there is some plan to have Language Server Protocol (LSP) support for AsciiDoc since it would greatly benefit markup language since all the major editors have LSP clients?


Sincerely,
Gour


If you reply to this email, your message will be added to the discussion below:
https://discuss.asciidoctor.org/AsciiDoctor-LSP-support-tp8397.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML


--
Dan Allen (he, him, his) | @mojavelinux | https://twitter.com/mojavelinux
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor & LSP support

gour
On Fri, 18 Dec 2020 14:19:38 -0700 (MST)
"mojavelinux [via Asciidoctor :: Discussion]"
<[hidden email]> wrote:

> I definitely recognize the need and benefit of having an LSP impl,
> but we also must be honest. Not all major editors use it.

Hmm, Vim has several LSP clients, Neovim is getting a native built-it one,
Emacs also has, two major clients...Atom has LSP support and, as you mentioned,
Sublime as well. Even Kakoune editor has it, so, imho, to make AsciiDoc more
widely used, having LSP is a must.



Sincerely,
Gour

--

attachment0 (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor & LSP support

mojavelinux
Administrator
I'm glad to hear there's strong support for this idea. Obviously, anything we can do to broaden adoption of AsciiDoc is great in my book. That's why I do what I do. I'm looking forward to your participation in this effort.

Best Regards,

-Dan

On Sat, Dec 19, 2020, 02:47 gour [via Asciidoctor :: Discussion] <[hidden email]> wrote:
On Fri, 18 Dec 2020 14:19:38 -0700 (MST)
"mojavelinux [via Asciidoctor :: Discussion]"
<[hidden email]> wrote:

> I definitely recognize the need and benefit of having an LSP impl,
> but we also must be honest. Not all major editors use it.

Hmm, Vim has several LSP clients, Neovim is getting a native built-it one,
Emacs also has, two major clients...Atom has LSP support and, as you mentioned,
Sublime as well. Even Kakoune editor has it, so, imho, to make AsciiDoc more
widely used, having LSP is a must.



Sincerely,
Gour

--

attachment0 (849 bytes) Download Attachment



If you reply to this email, your message will be added to the discussion below:
https://discuss.asciidoctor.org/Re-AsciiDoctor-LSP-support-tp8404p8405.html
To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML
Reply | Threaded
Open this post in threaded view
|

Re: AsciiDoctor & LSP support

Alexander Schwartz
In reply to this post by mojavelinux

Hi, I'm the current maintainer of the IntelliJ AsciiDoc plugin.

The IntelliJ plugin for AsciiDoc doesn't use LSP, it uses the native JetBrains functionality to provide editor and preview support. It builds upon lexing/parsing/indexing infrastructure of the JetBrains platform.

A future LSP implementation could benefit from the work done here in some ways:

  • The plugin has a documentation site outlining its features. This might help to grow ideas what a LSP implementation could support. I'm happy to join a discussion for a MVP (minimum viable product).
  • There is a chance to reuse/refactor some of the code of the plugin as long as people are willing to use Java (maybe Quarkus) to implement their LSP. Some lexing/parsing might be re-used, again I'm open to talk.
As my day-to-day IDE is IntelliJ, I miss the benefits of driving LSP and lack the experience in other editors. So it would need someone to drive LSP forward. I will support this person or group of people in every way I can. Please note that AsciiDoc is currently a spare-time activity for me.

Regards, Alexander

Alexander Schwartz (alexander.schwartz@gmx.net)
https://www.ahus1.de