superbol-studio-oss
superbol-studio-oss copied to clipboard
OCamlPro
Open-Source part of the SuperBOL Studio, including the Vscode mode with LSP
As of now the tests do not pass, the diffs are as follow, I have yet to understand why: ```diff File "test/lsp/lsp_formatting.ml", line 1, characters 0-0: diff --git a/_build/default/test/lsp/lsp_formatting.ml b/_build/default/test/lsp/lsp_formatting.ml.corrected...
Just stumbled over that page when searching for GC docs :-) Feel free to close as "not planned" if this isn't appropriate.
The only other problems concerning world cities are the `>>D` compiler directive and the order of the paragraphs in the environment division (worldcities uses `repository` before `special-names` which is not...
> if you adjust something there, then make it compatible to COBOL2023.  (that is not 100% correct, the "..." applies to both argument-2 and `ANYCASE` together. * argument-2 may...
In the [GnuCOBOL doc](https://get-superbol.com/gnucobol/manual/chapter2.html#debug-switches), a `-fdebugging-line` option is defined for debugging. The `D` indicator (in the 7th column) is recognised by the LSP but not the `>>D` directive (which exists...
While running inside VScode, we could use [ExtensionContext.storageUri](https://code.visualstudio.com/api/references/vscode-api#ExtensionContext.storageUri) to store data instead of having extra `_superbol` directories everywhere.
This way people can easily test work-in-progress, without the need to checkout + build themselves. This is possibly something for either @nberth or @lefessan. The REAMDE _may_ reference this on...
Emacs can use vscode compatible DAP-adapters - can you please investigate and document _how_ to use the superbol-vscode-debug (which may need adjustments or splitting into a sub-module/repo)? Once this is...
This PR adds the required utils for connecting vscode editor to a remote LSP.
