Torsten Paul

There's `scripts/beautify.sh` running the `uncrustify` tool using the configuration file on top level of the repo. If it runs in a branch it tries to touch only the files modified...

Win64: https://app.circleci.com/pipelines/github/openscad/openscad/2890/workflows/25033df3-d2e3-4417-a053-e7fce1ec9a80/jobs/12116/artifacts Grab it, while it's still hot, I'm not sure how long they store the builds :grin:.

With the `object` discussion haing a diffent focus regarding the syntax, would it make sense to move this (and similar recent #4294) to focus on dictionary as discussed some time...

cc @adam-trhon

Ref: https://lists.openscad.org/empathy/thread/3DVXSTCBWJPKPUVBJBFMMQ27BVYUS352

Modifying the parser is fine, we just need to try to not cause issues with the existing syntax. Using bison does introduce a couple of restrictions on what is possible....

Different effect on Linux, trying to close the window will just close it for a second but it directly shows as floating again.

Getting only 404 on that repository, is it set to private?

Yeah, I was wondering about the 565 color support. We do need depth and stencil buffers, but that reporting seems unreliable. On my local machine (Dell XPS 13 running Debian/Testing)...

Hmm, and with even more variables added (second one probably not needed): ``` GALLIUM_DRIVER=softpipe LIBGL_ALWAYS_SOFTWARE=true ``` That might make everything extremely slow with the softpipe rendering but just to see...