Rich Felker

Note that this workaround no longer works: > So my proposed workaround is to put the waits (without a specific temperature, indicating "wait for the current target temp") in the...

As far as I know, CuraEngine has no way to request generation of that sequence. You have to edit the resulting gcode or put temperatures in the start gcode (CuraEngine...

@dybvig, so what needs to be done to make this work? `time_t` is now 64-bit on all our archs.

> e.g., the choice of libc could be changed at build time, i.e., after configure The "choice of libc" **is the target**. There's no plausible way you support it changing...

> No, I'm pretty sure that this glibc documentation ... does not govern what you can do with non-glibc implementations, and no, you absolutely can't do that. If you just...

Indeed such a page would probably be appropriate for the wiki. Patches should be submitted to the mailing list, but when the patch is not just a bug fix but...

I think scripts are definitely the right approach here. A good starting point might be a script to enumerate the settings that presently have overrides in one or more printer...

I suspect the opposite would be more appropriate: an allow-list of things that can go in printer profiles, and a unit test that checks that they don't have anything not...

Related: wipe moves at the end of the outer wall are also applied with the travel acceleration. This is not as bad, since in theory nothing new is being printed,...

It looks like netbsd curses is internally mixing byte and wide stdio calls, which produces undefined behavior. See at least: https://github.com/sabotage-linux/netbsd-curses/blob/ae69600380da3e0a8ea509fee65dbd5575a34daa/libcurses/putchar.c#L62-L92 I think you want to use narrow stdio functions...