Document latest features

[nberth]

Document code lens, symbol renaming and CFG explorer.

[emilienlemaire]

Looks good to me, just a few too many spaces 😃

[engboris]

Some typos

[nberth]

Looks good to me, just a few too many spaces 😃

That's a habit I kept from the time I edited LaTeX: it's actually very useful to distinguish sentences, and has no impact on markdown semantics.

[GitMensch]

This section misses things like attaching, setting program/procedure breakpoints, watchpoints, ...

If you change the extension to keep the debugging in its own separate extension (with a dependency in this extension to the debug extension but not vice-versa if the other extension does not use the LSP), then you'd only need a teaser here and can reference to that's extension's README, which should already include parts of this.

Also I'd highly suggest to not only hint to the debug build task, because that is only useful for small/testing programs [
but there it is very useful, especially for beginners]. With bigger environments you'll have either external build flows or (most preferably) done it by make.

For this scenario it is important to document which options need to be passed to cobc (I think for GC 3.2+ the -g option is enough).

As the coverage handling is also part of that extension, the same applies there - but in any case I'd suggest to have at least a screenshot of that here.

[nberth]

I've added basic details about the additional flags passed to cobc.

Regarding dependencies, at the moment the debug extension is tuned with a preLaunchTask that directs to a build task of the main extension; this is mainly to help newcomers (they can just press F5 to automatically compile and run programs). I'd like to keep the extensions separate, but for now we found no convincing way to do that and keep the aforementioned behavior (it's also still debatable whether this fully automated behavior is really worth the hassle — see also the other debug-related issues).

At the moment I'm trying to do a quick release (long overdue); so aspects mentioned in this comment will be addressed later.

Note we don't rely on the debug extension to show coverage information (there's no reason to have those two features so tied together I think): a dedicated gcov-viewer extension that we found simpler/more maintainable than the coverage-related code of the debug extension is used instead.

[GitMensch]

a dedicated gcov-viewer extension that we found simpler/more maintainable than the coverage-related code of the debug extension is used instead.

That's good - can you keep that in a separate (depending = automatically installed [as long as you're connected to the internet]) extension or does that needs to "included" as well?

Please create an issue to drop the coverage stuff from the debugging extension (because it is not needed any more and is "too much" there as well).