Eldred Habert

> Yes, exposing POSIX and C11 APIs at the same time is inherently contradictory. That's a stance I could never fully understand: extensions to the standards exist, so why couldn't...

A further comment in that thread notes that this is only an implementation detail of libstdc++, whose C++ headers define `_GNU_SOURCE`. I'm not sure that's portable to other C++ libraries?

Doesn't `-x` already add blank tiles to the end of the input? If not, maybe that should be added. As for guessing the input size, unless the image is perfectly...

Yes, but my point is that if you specified `-x` as input, you can also specify the same in "reverse mode". Those wouldn't be accurate to the original data, since...

Then the best guess to take is 1, which is equivalent to `-r 1`. Is it not sufficient to view the file, press up in the terminal, change the argument...

The plan is indeed to RIIR (#1213), and also to switch to libplum since it provides the functionality we are interested in (in particular, palette-aware image loading) but also support...

Isn't it sufficient to generate the palette with `-c embedded`, ignore the attributes, and truncate the palette data? ```console $ rgbgfx -c embedded -p >(dd of=testcase1.pal bs=8 count=1 status=none) -o...

> 1. What does `>(` do? I don't know how to search the manual for punctuation. Web search engines strip punctuation, and searching within `man bash` on Ubuntu 22.04 gives...

I think the errors are caused by `-c embedded` only accepting 4 input colours, instead of all. I'll have to look into that.

This is why: https://github.com/gbdev/rgbds/blob/a47da5f71f1b755b3a2fa03736cda60534dfb639/src/gfx/process.cpp#L567-L569 So if I'm understanding correctly, this should instead be: ```cxx if (embPalSize > options.maxOpaqueColors() * options.nbPalettes) { fatal("Too many colors"); } ``` , right?