Boris Eng

The fix will be part of the next release (very soon). Thank you for your contribution!

The fix will be part of the next release. Thank you for your contribution!

Hello Michael. We're investigating the problem with our team. We did some tests (VSCode extension with debugger and an external terminal to communicate with the program) and could not reproduce your bug. We suspect a problem specific to Windows. The best you can do would be to open a Git issue here with details about your problem and environment to help us reproduce the bug: https://github.com/OCamlPro/superbol-studio-oss/issues

I believe tab stops should already work if the file is correctly detected as a COBOL file. For more configuration, I think it's managed by VSCodium. On the bottom of VSCodium, there's something like "Spaces: 8" on which you can click on. Then should be able to choose tab/spaces, tab display size etc. For copybooks locations, I already sent you the instructions by email. You can go in the settings.json of the extension and change { "superbol.cobol.copybooks": [ { "dir": "." } ] } "dir": "." tells...

You should only choose one. Studio Pack is the SuperBOL Studio extension + other useful extensions. For the moment, it comes with a TOML extension to make advanced configuration easier. SuperBOL Studio OSS is lighter and should be enough if you don't have needs regarding advanced configurations.

If the extension is correctly installed, it should provide syntax highlighting and other features out of the box, without requiring any additional configuration. It also offers useful capabilities such as automatic detection of certain errors. The issues you’re experiencing may be related to VSCodium itself rather than to the SuperBOL Studio extension. That said, I completely understand that VSCode/VSCodium can feel overwhelming if you’re just getting started. What code editor were you used to b...

If the extension is correctly installed, it should provide syntax highlighting and other features out of the box, without requiring any additional configuration. It also offers useful capabilities such as automatic detection of certain errors. The issues you’re experiencing may be related to VSCodium itself rather than to the SuperBOL Studio extension. That said, I completely understand that VSCode/VSCodium can feel overwhelming if you’re just getting started.

Normally, syntax highlighting is always enabled for COBOL files (provided that you have installed the SuperBOL Studio OSS extension and that it is enabled). The extension detects COBOL files based on their extension (.cob, .cbl). Could it be that your files use a different or no extension at all? For more settings, you can go in the Extensions tab (Ctrl + Shift + X) on the left panel. From there, either click the gear icon or right-click on the SuperBOL Studio OSS extension and select Settings to...