pascal-language-server
pascal-language-server copied to clipboard
genericptr
LSP server implementation for Pascal
I cannot get pasls works properly. I'm using the newest version of pasls, compiled on macOS m1, after config and launch the lsp, en error message in lsp log indicate...
With a build of the latest `trunk`, the language server claims to support a very limited set of capabilities: ``` "capabilities":{"referencesProvider":false,"executeCommandProvider":{"commands":["pasls.formatCode","pasls.completeCode","pasls.invertAssignment","pasls.removeEmptyMethods"]},"documentHighlightProvider":false,"hoverProvider":false,"workspaceSymbolProvider":false,"declarationProvider":false,"signatureHelpProvider":{"triggerCharacters":[]},"documentSymbolProvider":true,"definitionProvider":false,"workspace":{"workspaceFolders":{"changeNotifications":false,"supported":false}},"textDocumentSync":{"save":{"includeText":false},"willSaveWaitUntil":false,"willSave":false,"change":1,"openClose":true},"codeActionProvider":false,"completionProvider":{"allCommitCharacters":[],"resolveProvider":false,"triggerCharacters":[]},"implementationProvider":false} ``` For example, since `"referencesProvider":false`, the language server claims...
Im unable to build this project with the thing in the README so are there any prebuilt binaries for windows?
hi, i really would like to try this lsp out in neovim, right now im trying to compile it, yet i get this error:  I have followed the "Building"...
Hey Ryan(@genericptr), When I finally came around to test this, since I'm now using Sublime-Text, I saw some issues. The double `/` and the read errors I've addressed in #82....
We're using a client based hack now which works for ST and VSCode but we should probably implement this correctly by providing version numbers.
Right now absolute paths are used which is wasteful and prone to break if the project is moved.