Follow up question… Assume the LSP is for language editing mainly but how do linking with a given compiler and/or run type action get handled?
Assume there may be need to handle setting up instances of a given languages compiler/runtime so where is this setup? Depending on the language assume there may be need for additional plug-in/module management support (i.e. node module, Python pips, etc.). Or would this be in someway some kind of dependency handling functionality for the language? If in the past there was an older implementations for a given language, is it better to start over, to convert over to an LSP based merging code when possible or just maintain the existing updating to current standards? Assume this depends on the implemented language but figure I’d add as an extra step to start porting languages. On Fri, Oct 8, 2021 at 7:34 AM Eric Bresie <[email protected]> wrote: > I’ve seen the tutorial and appreciated the context, but was curious if > more generalized perspective can be expanded on as this is a specific > implementation. Some of the following may be implied by the article > indirectly but wanted to confirm it here as well. > > It talks about setting up a node.js bash LSP server. So in general, does > each language need some sort of equivalent LSP Server ? Or does the > provided LSP in Netbeans work well enough to support other languages? > > Assume if a server is not available then one may need to be implemented. > Assume to do this would require compliance with LSP interface of some type > and if so where can this be found? Is there interface defined in Netbeans > which can be extended or implemented from? > > If an server is available how should that be brought in? Add a dependency > which gets pulled in with maybe some wrapper layer having it? > > In what context does the “server” get started up/loaded within Netbeans? > Are there specific triggers to start it (i.e. when working on a specific > file type of the given language, if the language support is “active”, at > startup, or some other trigger)? > > I seem to recall in the preference section there is the ability to define > an LSP support. How does this interact with the new language implemented > here? In other words, does something have to be defined and added so that > it includes in that area? Does the user have to manually define that (I > would hope not but maybe initially) and link up the LSP? > > How is the grammar (tm) linked up? Is that supported by the server or > does the server link to the external grammar? So if there is an “external > implemented server”, does this mean limited or no coverage of the grammar > would have to be considered? > > What client interfaces need to be implemented and where are they defined? > Does the client also need knowledge of the grammar in some way? > > Assume the “mime-type” may need to be based on standardized ‘mime-types” > for a given language. Is there a sources to use to get these > “mime-types”? Can always google but if there is someplace already > established with these to base on that may also help some. > > > On Thu, Oct 7, 2021 at 1:18 AM Jaroslav Tulach <[email protected]> > wrote: > >> > - LSP <https://langserver.org/> seems to be gaining ground, but >> there >> > are no tutorials, apart from Jan Lahoda's rudimental one >> > <https://blogs.apache.org/netbeans/entry/lsp-client-demo-ba-sh>. >> >> >> Why do you call the tutorial "rudimental"? The tutorial is short, but it >> contains grammar, syntax coloring, and LSP server. E.g. everything. >> Shouldn't >> you rather call the tutorial "end-to-end" guide for integrating languages >> into >> NetBeans via LSP? >> >> -jt >> >> PS: The only question is why people don't follow the tutorial and create >> a new >> PR with a new language integration per week? >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> For further information about the NetBeans mailing lists, visit: >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >> >> >> >> -- > Eric Bresie > [email protected] > -- Eric Bresie [email protected]
