One thing that I think would be really useful is a Language Service Provider for Clascal, so the Lisa sources can be more easily browsed in tools like BBEdit, Visual Studio Code, and so on.
Also, here’s some stuff I’ve done to my own copy of the sources. (Sorry I can’t share them, I have some employer-related rules I need to follow…)
- Put the sources as-is into a local git repository so I can commit every subsequent change in case I screw something up.
- Get rid of all the Lisa-format text files, since they’ve all been converted to UNIX text.
- Get rid of the “.unix.txt” extensions on all of the UNIX text format files, so they all have “.TEXT” as a suffix again.
- Replace the “.TEXT” suffix where possible with a semantic suffix: “.pas” for Pascal/Clascal code, “.asm” for 68K assembly code, “.exec” for EXEC scripts, “.alerts” for alert definitions, and so on.
Having done all of that I now have a nicely-browsable version of the code that actually gets some degree of syntax highlighting and so on. What LSP would provide is better syntax highlighting for Clascal constructs, as well as being able to jump to definitions and such.
