Adam Babik

@hamza-tam totally we can. We are in the middle of some bigger changes for a new use-case but I will try to incorporate your PR this week.

You can achieve this by adding `sh {name=n}` at the top of your snippet right after the backticks. I think it might be confusing and unexpected for some people to...

@sourishkrout of course, we can exclude internal/private attributes. I was thinking either of `_` or `runme.dev/*`. Let me know which way you want to go.

@sourishkrout if `_` is unused by VS Code, we can use `_` as it's shorter. If `_` is already used and we want to have more control then `runme.dev/*`.

@nitsanavni thank you! That's one of the options we consider. More broadly, we are looking into long-lived interactive sessions similar to a concept of Kernel from Jupyter Notebooks.

We just released version v0.5.0 which has an interactive mode! 🎉 Please update runme (confirm with `runme --version` that it is v0.5.0 indeed) and try running `runme` or `runme tui`....

@sourishkrout I presume it's a problem in the extension which converts code cells with an unsupported lang to markdown cells. At least [the current main](https://github.com/stateful/vscode-runme/blob/main/src/extension/notebook.ts#L129-L137) suggests that. I run `./runme...

@sourishkrout I tried https://github.com/stateful/vscode-runme/pull/81/commits/2169911c39f1a18af0592992f9840a44415dad9d and I cannot reproduce it. This is the diff after serialization: ```` These are shown as simple markdowns, e.g: -```py { readonly=true } +```py {name=def-hello index=41...

I tested it quickly and it looks ok with `run-locally`. I think you can test it yourself: ``` # in /path/to/github.com/stateful/vscode-runme $ runme --version runme version 2.2.6 (Homebrew) on 2024-02-09T17:53:40Z...

AFAIR we definitely wanted to make sure that the API stays backward compatible, which should be enforced in the API. Checking the contract here is too late. However, provided that...