Running the language server with other editors

[archseer]

The language server is currently a bit difficult to run if using a different editor than VSCode. I already have gotten tree-sitter highlighting to work in Helix but I'd also like to provide a language server config. Making the language server easy to install (or at least have it's own package.json) would help with usability

[archseer]

It would also be good if the tolkSdk path was specifiable via the InitializationOptions of the language server (same as wasm & tree sitter grammar path) so that we could avoid defining non-standard requests (tolk/detectSdkForFile)

[archseer]

Hmm similar for fileReadContents, why not have the LSP read this directly?

[archseer]

Attempting to run with a couple messy patches but I can't seem to get any completion for stdlib, I do see it load common.tolk:

diff --git i/server/src/document-store.ts w/server/src/document-store.ts
index 4655848..e6f1556 100644
--- i/server/src/document-store.ts
+++ w/server/src/document-store.ts
@@ -4,6 +4,7 @@ import { TextDocuments } from 'vscode-languageserver';
 import { TextDocument } from 'vscode-languageserver-textdocument';
 import { LRUMap } from './utils/lruMap';
 import { NotificationFromClient, RequestFromServer } from "./shared-msgtypes";
+import { readFile } from "node:fs/promises";
 
 export interface TextDocumentChange2 {
   document: TextDocument,
@@ -77,12 +78,26 @@ export class DocumentStore extends TextDocuments<TextDocument> {
   }
 
   private async _requestDocument(uri: string): Promise<TextDocument | undefined> {
-    const reply = await this._connection.sendRequest<{ type: 'Buffer', data: any } | { type: 'not-found' }>(RequestFromServer.fileReadContents, uri);
-    if (reply.type === 'not-found') {
+    uri = decodeURIComponent(uri);
+    let prefix = "file:///"
+    if (uri.startsWith(prefix)) {
+      uri = uri.slice(prefix.length);
+    }
+    console.error(uri);
+    try {
+      let data = await readFile(uri);
+      let decoded = this._decoder.decode(new Uint8Array(data));
+      console.error(data);
+      return TextDocument.create(uri, 'tolk', 1, decoded);
+    } catch (err) {
+      console.error(err);
       return undefined;
     }
-    let decoded = this._decoder.decode(new Uint8Array(reply.data));
-    return TextDocument.create(uri, 'tolk', 1, decoded);
   }
 
 }
diff --git i/server/src/tolk-sdk-mapping.ts w/server/src/tolk-sdk-mapping.ts
index 6fa44e1..06f0702 100644
--- i/server/src/tolk-sdk-mapping.ts
+++ w/server/src/tolk-sdk-mapping.ts
@@ -20,11 +20,17 @@ export class TolkSdkMapping {
       return this.tolkSdk[uri]
     }
 
-    let tolkSdk = await connection.sendRequest<TolkCompilerSDK | null>(RequestFromServer.detectSdkForFile, uri)
-      .catch(ex => {
-        console.error(ex);
-        return null
-      })
+    let tolkJsFolder = "../node_modules/@ton/tolk-js";
+    let tolkSdk: TolkCompilerSDK = {
+      detectedMethod: 'node_modules',
+      tolkCompilerVersion: "0.13.0",
+      stdlibFolder: tolkJsFolder + '/dist/tolk-stdlib'
+    }
 
     if (tolkSdk) {
       // tolkSdk for file has been detected; now we know compiler version (what syntax features are enabled)

[archseer]

@tolk-vm Can you take a look?

[Trinketer22]

I'm looking into it to, hopefully, speed things up for you.
@tolk-vm is currently occupied with the actual compiler release

[Trinketer22]

Here is a very basic workaround:https://github.com/Trinketer22/tolk-lsp-server?tab=readme-ov-file#helix
I did test it locally with helix, please try it out, and feel free to lmk if it doesn't work for you in any way.

It supports very basic stuff (same as vscode one).
We will certainly improve the LSP experience as soon as the major compiler release is settled.

[archseer]

Awesome, thank you! It seems to work for me 👍🏻 You could technically still use lsp init arguments rather than CLI args, since that part is widely supported, I was using this config before:

config = { treeSitterWasmUri = "vendor/tolk-vscode/dist/tree-sitter.wasm", langWasmUri = "vendor/tolk-vscode/dist/tree-sitter-tolk.wasm" }

[Trinketer22]

Oh! Point taken! i'll map cli args into lsp init in that case