I am trying to get back into working GnuCOBOL. The Bitlang: COBOL extension does not work anymore code color highlighting. It works fine when I have to do RM/COBOL (supporting an application).
I have noticed SuperBOL. I have tried to install the extension, but having a little trouble using it.
Is there any other suggestions or a resolution Bitlang: COBOL?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2025-09-19
The bitlang extension has support for RMCOBOL dialect.
Yes, the point was that bitlang.cobol is working fine with the RM/COBOL sources but not working with GnuCOBOL (it used to and that was a good time, then this was moved out and later checked and blocked).
Do you suggest we create an issue "Bring GnuCOBOL support back to bitlang.cobol?"
If there is a chance for that being done, then I'm totally happy with that and can suggest people to use that if they don't want or need any of the GnuCOBOL debug specific parts of superbol (possibly disabling all the JCL and other stuff in the bitlang.cobol extension settings that are not relevant for PC COBOL that did not use an Enterprise emulation).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you don't use any of the RM/COBOL specific features (are there any?) in bitlang.cobol, then I'd suggest to remove it (this way you also don't have a "conflict", which I think bitlang.cobol is still picky about).
If you have any issues with the superbol extension (which I use locally) then please create an issue at its own tracker, where you possibly also find information already how to do whatever you have trouble with: https://github.com/OCamlPro/superbol-studio-oss/issues
Its debugging part also works "in general" (still not for my employer's setup, but it will get there; already better than the gnucobol-debug extension which that part is based on).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello! I’m from OCamlPro (the developers of SuperBOL Studio).
Thanks a lot for trying out our VSCode extension. We’d love to hear more about the issues you’ve encountered so we can improve it and make the experience as smooth and enjoyable as possible. You can also reach us at superbol@ocamlpro.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 access additional configuration options.
Please don’t hesitate to let us know if something is missing. We may have overlooked a specific use case.
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 you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 before?
Last edit: Boris Eng 2025-09-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, believe it or not, the mention of "cobol-mode" got me thinking and I noticed that the Language Selection was set to "Plain Text". I then went to the settings.json and modified the "File Associations" to "cobol". Syntax Highlighting is working.
Is there a setting for tab stops?
How do I set the location for the copybooks locations. I currently use GnuCOBOL symbol COBCPY. I have tried plain, % and $ to no avail.
Is there a document for SuperBOL with examples?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I looked at your screen shot.
I would presume that SUPERBOL is Linux only - correct ?
The examples indicate lower case file extensions.
Are they folded to upper case when necessary
For instance a copy book is not found convert from .cpy to .CPY
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could use -ffold-copy (and -ffold-call) and the extensions may also be adjusted to use both upper and lower case (which is the default for cobc, so superbol may should use the same default to be less confusing for people on Linux (@nberth what do you think?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I confirm that by default the behavior of SuperBOL Studio matches cobc with -ffold-copy: copy foo will look for a copybook named foo.CPY as well if foo.cpy is not found.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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
After re-reading the README.md file again and again, I was able to get copybooks working by hardcoding directories. I would like to suggest a feature that symbols like COBCPY be used to point to all the copybook locations.
I would like to suggest another feature to set tab stops at specific locations.
Boris thank you for your help and patience. I would like to thank all those you took part in this discussion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
... but I agree that a superbol.tabstops setting that catches TAB/SHIFT+TAB and positions to specific columns using space characters would be nice (maybe if enabled with a different setting to not override "common expectations" by default).
"intelligent tabstops" that would align to the previous non-comment line would be superior, so maybe go with that instead.
(side note: the superbol issue tracker is likely the better place to ask for specific features ;-) - especially: to track them)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does COB_COPY_DIR still only deliver the first node in the concatenation to the compiler
SET COB_COPY_DIR=C:\WINZOS\COPYBOOK;\IBZANIM\COPYBOOK;^
Any specification beyond the first semi colon or space is ignored by the compiler ?
Ralph
Last edit: Ralph Linkletter 6 days ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to get back into working GnuCOBOL. The Bitlang: COBOL extension does not work anymore code color highlighting. It works fine when I have to do RM/COBOL (supporting an application).
I have noticed SuperBOL. I have tried to install the extension, but having a little trouble using it.
Is there any other suggestions or a resolution Bitlang: COBOL?
The bitlang extension has support for RMCOBOL dialect.
You can also raise issues @ https://github.com/spgennard/vscode_cobol/issues
Yes, the point was that bitlang.cobol is working fine with the RM/COBOL sources but not working with GnuCOBOL (it used to and that was a good time, then this was moved out and later checked and blocked).
Do you suggest we create an issue "Bring GnuCOBOL support back to bitlang.cobol?"
If there is a chance for that being done, then I'm totally happy with that and can suggest people to use that if they don't want or need any of the GnuCOBOL debug specific parts of superbol (possibly disabling all the JCL and other stuff in the bitlang.cobol extension settings that are not relevant for PC COBOL that did not use an Enterprise emulation).
If you don't use any of the RM/COBOL specific features (are there any?) in bitlang.cobol, then I'd suggest to remove it (this way you also don't have a "conflict", which I think bitlang.cobol is still picky about).
If you have any issues with the superbol extension (which I use locally) then please create an issue at its own tracker, where you possibly also find information already how to do whatever you have trouble with: https://github.com/OCamlPro/superbol-studio-oss/issues
Its debugging part also works "in general" (still not for my employer's setup, but it will get there; already better than the gnucobol-debug extension which that part is based on).
Hello! I’m from OCamlPro (the developers of SuperBOL Studio).
Thanks a lot for trying out our VSCode extension. We’d love to hear more about the issues you’ve encountered so we can improve it and make the experience as smooth and enjoyable as possible. You can also reach us at superbol@ocamlpro.com
I do get syntax highlighting working?
BBEdit on my mac gives syntax highlighting for .cob files.
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 access additional configuration options.
Please don’t hesitate to let us know if something is missing. We may have overlooked a specific use case.
You can find more information on the README file of the extension: https://github.com/OCamlPro/superbol-studio-oss
Last edit: Boris Eng 2025-09-25
What is the difference between the Studio OSS and Studio Pack? Can you have both?
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.
yes, i removed the studio pack one and the regular one works ok. thanks
Simple.
M-x cobol-mode
:)
Marco Antoniotti
https://dcb.disco.unimib.it
On Fri, 19 Sep 2025 at 21:54, Rich Di Iulio trolley78@users.sourceforge.net
wrote:
I give up, SuperBOL does not work for me. I appreciate people trying to help me, but no luck. I may need to find something other than Codium to work.
I need tab stops, syntax highlighting. mono chrome makes my eyes get tired quickly.
Again, is there any extensions that work with GnuCOBOL.
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 before?
Last edit: Boris Eng 2025-09-26
Okay, believe it or not, the mention of "cobol-mode" got me thinking and I noticed that the Language Selection was set to "Plain Text". I then went to the settings.json and modified the "File Associations" to "cobol". Syntax Highlighting is working.
Is there a setting for tab stops?
How do I set the location for the copybooks locations. I currently use GnuCOBOL symbol COBCPY. I have tried plain, % and $ to no avail.
Is there a document for SuperBOL with examples?
Forgot to add, I have been using VS Codium since it arrived on the scene.
Please go to the extension overview and click on superbol , then have a look at all the documentation there under "Details" - or read the same under https://github.com/OCamlPro/superbol-studio-oss/blob/master/README.md
Also you want to go to to "Features" and there to "Settings" (See attached screenshot)
Last edit: Mickey White 2025-09-26
I looked at your screen shot.
I would presume that SUPERBOL is Linux only - correct ?
The examples indicate lower case file extensions.
Are they folded to upper case when necessary
For instance a copy book is not found convert from .cpy to .CPY
Ralph, It apparently is for windows also.
You could use
-ffold-copy(and-ffold-call) and the extensions may also be adjusted to use both upper and lower case (which is the default for cobc, so superbol may should use the same default to be less confusing for people on Linux (@nberth what do you think?)I confirm that by default the behavior of SuperBOL Studio matches
cobcwith-ffold-copy:copy foowill look for a copybook namedfoo.CPYas well iffoo.cpyis not found.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
"dir": "."tells the extension that copybooks are located in the current directory. You can change"."for another path.You can find more information here: https://github.com/OCamlPro/superbol-studio-oss?tab=readme-ov-file#editing-an-existing-project
and scroll down to
The path to copybooks "superbol.cobol.copybooks".After re-reading the README.md file again and again, I was able to get copybooks working by hardcoding directories. I would like to suggest a feature that symbols like COBCPY be used to point to all the copybook locations.
I would like to suggest another feature to set tab stops at specific locations.
Boris thank you for your help and patience. I would like to thank all those you took part in this discussion.
Just to note: you may want to add the following configuration
to get "visual" rulers for COBOL sources, if you are a fixed-format guy (that may be useful for superbol's README as well).
If you want a "special" coding, you may try https://marketplace.visualstudio.com/items?itemName=gerold-meisinger.elastic-tabstops-lite-redux (with its "use space" setting)
... but I agree that a
superbol.tabstopssetting that catches TAB/SHIFT+TAB and positions to specific columns using space characters would be nice (maybe if enabled with a different setting to not override "common expectations" by default)."intelligent tabstops" that would align to the previous non-comment line would be superior, so maybe go with that instead.
(side note: the superbol issue tracker is likely the better place to ask for specific features ;-) - especially: to track them)
Does COB_COPY_DIR still only deliver the first node in the concatenation to the compiler
SET COB_COPY_DIR=C:\WINZOS\COPYBOOK;\IBZANIM\COPYBOOK;^
Any specification beyond the first semi colon or space is ignored by the compiler ?
Ralph
Last edit: Ralph Linkletter 6 days ago