The Gram Code Editor - 2026-06-06

Well, at any rate, it is by certain measures quite successful. Meanwhile, a static list of options per language can be quite limiting. It would be useful if extensions could provide further customized automation. Extensions are also useful that can interact with external tools, not just version control and debuggers, but build and test frameworks, or anything that can live inside a project or interact with a project.

There is already the task system to interact with external tools like test frameworks, I would prefer to improve that if it is lacking in some way.. but personally I don’t use it at all so probably won’t be a priority for me. I tend to use external tools via the terminal.

https://chat.slidge.im:5281/file_share/019e9bf6-b646-77f8-892e-db082e594cf3/ce938a65-fb8b-416b-96db-4fb1906d962e.png

I hope we don't lose this integration of pytest ^

I understand if it's too much maintainance burden but man, I do use that a lot. Writing a debug entry in debug.jsonc for each test is possible, but quite tedious.

It would be nice to make it more extensible yeah, right now the python support is hard coded and specific. Would be nice to be able to add that via extensions

It does not sound great to hardcode support for python tools indeed. Since I do python 99% I don't mind at all, quite the opposite though. ^^

Hopefully this becomes an extension and I can try to improve it though. Working on an extension is less scary than touching the large rust codebase :)

PyCharm (=JetBrains) had a pretty nice, deeper, integration of pytest which sucked by some aspects but had one killer feature (for me at least). You could run the whole test suite, then specifically had an option to "re-run failed tests only". I miss that a bit.

oh yeah that would be nice to have