You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OCamlPro.SuperBOL is nice and commonly usable.
It likely has some issues with vscode-web (see also #188), but even with a WASM server (which seems to be a long shot) it may not work in "minimal environments".
I'm currently having fun in a minimal reh environment where the remote extension host does not work.
At least in cases like this an OCamlPro.SuperBOL-mini would be nice to have a version that has no need to run there (=local editor). This would likely mean:
no native LSP interaction
using only the open editor window(s)
Can you provide an extension like this (=taking this one and deleting all parts that would need to run "wherever the code is", reducing it to the local editor? ... maybe solve #193 first as that is implicit about "using the editor window instead of files"...
This would mean at least:
minimal syntax highlighting
problem matchers
un/comment line/block
possibly snippets
possibly "go to definition" using regex (= no REPLACE/COPY support)
The text was updated successfully, but these errors were encountered:
OCamlPro.SuperBOL is nice and commonly usable.
It likely has some issues with vscode-web (see also #188), but even with a WASM server (which seems to be a long shot) it may not work in "minimal environments".
I'm currently having fun in a minimal reh environment where the remote extension host does not work.
At least in cases like this an OCamlPro.SuperBOL-mini would be nice to have a version that has no need to run there (=local editor). This would likely mean:
Can you provide an extension like this (=taking this one and deleting all parts that would need to run "wherever the code is", reducing it to the local editor? ... maybe solve #193 first as that is implicit about "using the editor window instead of files"...
This would mean at least:
The text was updated successfully, but these errors were encountered: