Microsoft Language Server Protocol (LSP): A possible revolution for Notepad++?
Microsoft Language Server Protocol (LSP) defines the protocol used between an editor or IDE and a language server that provides language features like autocomplete, go to definition, find all references etc.:
Some cool editors are already making use of it, completely transforming the original editor being used for the communication with LSP:
I think that compatibility with LSP would give Notepad++ a huge boost towards acting as an IDE. Given any programming language, it could be possible for example to check for syntax errors in real-time, look for definitions, get some info through mouse hovering on a variable, etc. All of this into Notepad++. Here are some of the LSP-based existent projects, with the supported programming languages:
It seems that someone is already trying to implement LSP into Notepad++ by writing a specific plugin for it:
Someone else instead suggested to write a script in some language, for example, Python, by making use of the already existent “Python Script” plugin:
I think think this would lend to results similar to the ones achieved by this great plugin for Python programming in Notepad++:
So, I decided to open this thread to discuss the possible integration of Notepad++ with LSP. What do you think about it?
An LSP client for Npp would be AWESOME!!!
I’m kinda new to PythonScript plugin but from what I understand it should be possible
to create one but a dedicated plugin would be better, from my point of view, as it
could introduce the needed windows more easily. At least, I haven’t figured out how
to make this work using PythonScript plugin yet.
Yes, it would be awesome and, especially, a possible thing to do in Notepad++. The proper way to implement the LSP client into Notepad++ should, however, be discussed. Currently, some ways would be:
- By making use of Python Script
- Advantage: Ease of modification? Portability?
- Disadvantages: Slowness? Optimization?
- By writing a dedicated plugin
- Example: https://github.com/dail8859/NppLSP
I think Notepad++ is already the best choice when coding with some programming languages. Consider for example OpenEdge ABL, and see how this developer completely transformed Notepad++ into an IDE perfectly fitted for that language:
Many features were added with that plugin: a powerful auto-complete, linting, syntax checking, code browsing, go to definition, and so on… I just wished something similar to this existed for C/C++ (and many other languages), for Notepad++!
I’m curious to know how many people would be interested in an integration of Notepad++ with LSP because this, in my opinion, it would hugely expand the current capabilities of this almost excellent editor.
- By making use of Python Script
I’ve made some thoughts about implementing a LSP server.
All the cool stuff like auto-completion, signature help etc… aren’t part of this yet.
This is more about the general workflow and potential risks.
If someone has already read the specification or is aware how this is going to work,
or has general ideas, then I would appreciate any input.
Just in case it isn’t obvious - this would be the workflow for python code.
def On… are the callbacks which are triggered by npp, the init function
is the one which is going to be called as the very first function at all.
def __init__(): # read config file # create a dict of configured lspservers and their startup parameters # sanity check - check if known lspservers do still exist as file on disk # if not, log error and ignore config entry # create a dict of known languages npp/lsp # dict key notepad.getCurrentLang().name should return the lsp equivalent # def OnBufferActivated(args): # if notepad.getCurrentLang().name not in lspclient.dictOfLSPServers # return - nothing to do # else # if lspserver is not running # start lspserver # if process is running # send initialize request # wait for response (how long??) # if initialize response received # send initialized # else # what to do?? send a second time?? document says NO # ignore the lspserver for the rest of npp runtime?? # else # log error and (ignore the lspserver for the rest of npp runtime??) # # if didOpen was not already sent # send didOpen # else # send didChange ?? there seem to be no equivalent of buffer activated # should we send a didClose each time the active buffer changes?? # From the docs: # The document open notification is sent from the client to the server to signal newly opened text documents. # The document’s truth is now managed by the client and the server must not try to read the document’s truth # using the document’s Uri. Open in this sense means it is managed by the client. # It doesn’t necessarily mean that its content is presented in an editor. # An open notification must not be sent more than once without a corresponding close notification send before. # This means open and close notification must be balanced and the max open count for a particular textDocument is one. # Note that a server’s ability to fulfill requests is independent of whether a text document is open or closed. # # # The overall potential risk here is that it takes some time before a lspserver is completely started # which means the user might start typing and expects interaction which isn't possible at this time yet. # Maybe a startup parameter flag startLSPServer on npp startup could be helpful but this means lspserver # gets started even if it is not needed. # In addition, I assume that publishDiagnostics notification is send upon didOpen/Change notification # which would be another hint to have this run in its own thread but what if one constantly switches buffers? # I assume queuing and checking if the notification is still valid is needed. def OnFileBeforeSave(args): # send willSave notification # don't understand the meaning of the willSaveWaitUntil request. # Why should one allow to modify source code before closing the file - does not make sense to me. # From the docs # The document will save request is sent from the client to the server before the document is actually saved. # The request can return an array of TextEdits which will be applied to the text document before it is saved. # Please note that clients might drop results if computing the text edits took too long or if a server # constantly fails on this request. This is done to keep the save fast and reliable. def OnFileClosed(args): # send didClose notification def OnFileOpened(args): # normally we would send didOpen notification from here but because this callback is not reliable, # you won't see this callback on npp startup, we use OnBufferActivated callback to send the didOpen notification def OnFileSaved(args): # send didSave notification def OnLangChanged(args): # trigger an OnBufferActivated callback should be all we need to do, to be on the save side def OnReady(args): # maybe do some init here instead of atstartup.py - is it reliable?? def OnShutdown(args): # send shutdown request and exit notification