Dear extension author,
Please publish this extension to the Open VSX marketplace.

Context

Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products, we kindly ask that you take ownership of the VS Code extension namespace in Open VSX and publish this extension on Open VSX.

What is Open VSX? Why does it exist?

Open VSX is a vendor neutral alternative to the MS marketplace used by most other derivatives of VS Code like VSCodium, Gitpod, OpenVSCode, Theia-based IDEs, and so on.

You can read on about Open VSX at the Eclipse Foundation's Open VSX FAQ.

How can you publish to Open VSX?

The docs to publish an extension can be found here. This process is straightforward and shouldn't take too long. Essentially, you need an authentication token and to execute the ovsx publish command to publish your extension. There's also a doc explaining the whole process with an example GitHub Action workflow.

This might be a bit pedantic, but this seems like "live" debugging rather than real-time, especially since it's dependent on the underlying debugger as well (e.g. this chrome doc referring to 'live expressions' as near real-time)

The readme states the following:

Shows the text that was written to stdout next to the statement.

But I am not seeing this, only seeing it written to the debug console.

Is there anything particular I might need to do for non-JS/TS?

First of all, great extension! The statement highlighting and annotation of stdout-text work like a charm!

To make better use of the annotated stdout-text when editing I tried to keep track of document-changes and adjust the position of the annotations instead of deleting them. (#15) The PR is not tested properly but seems to work fine with the examples that I tried.

Is this a feature you'd consider implementing?

Also, I would like to have a command to set a logpoint that stores a local variable to global, so that you can later access the object in the debug console.

I think it would be cool if comments could set logpoints:

const x = new Obj(); // @log-ref
const y = 1 + 2; // @log: y

Since source maps are line based, the comment does not change anything. It could cause a recompile though.

In