Davy Landman

This was observed in v0.12.2 VS Code release. It has nothing to do with current changes to how we start the repl & pathconfig. But it could be that recent...

ouch, maybe this signals that the current implementation of join is not that useful, so nobody has run into specific bugs with it.

Hi @Ikke thanks, hmm, yeah, that sounds logical. Fun story, after all that work in getting that r8125 driver to compile and load (which was the manufactors recommendation for slow...

Hmm, yes, the discoverablity of the debugger is low, which was a bit intentional, as it has some strange behavior we're not completely happy with. But in many ways, it's...

> Another solution would be to activate the debugger when the first breakpoint is set. There were quite some limitations on how to start a debug session from VS Code,...

@urbanfly we should move this towards [usethesource/rascal-language-servers](https://github.com/usethesource/rascal-language-servers/) as there is where this new command is introduced in the REPL. For example here: https://github.com/usethesource/rascal-language-servers/blob/3d02641b265a7276082c34836545caf02ff50aa0/rascal-lsp/src/main/java/org/rascalmpl/vscode/lsp/terminal/LSPTerminalREPL.java#L111 But we should also try and change...

Closing this in favour of the following developments: - jline3 auto complete will include debug as a flag (with some help around it) - in VS Code we now have...

Similar for esphome 2022.9.4. I think maybe the manual should be updated to say ssl is not supported for esp8266, untill this upstream issue is resolved and esphome is migrated...

On web version we saw the same, but noticed if you use the scrollbars, instead of mouse scroll button/touchpad gestutr, it was a whole lot smoother.

Due to the low volume of changes in the parser, we don't run the parser test as part of the ci: https://github.com/usethesource/rascal/blob/30ab3a6f94b0b6d31b2b4e10e5dc85ac2d94e8a1/pom.xml#L247C1-L255C32