Paul Wessel

Before we do this, let's be clear on the scope. Another difference with **-C** is that **-F+c** clearance is either _gap_, _xgap/ygap_, or _lgap/rgap/bgap/tgap_ while **-C** is only _gap_ or...

Regardless of the above, I think +oxoff/yoff should be such that the corner of the rectangle touches that point. With -F+c now it is the zero-clearance imaginary rectangle that touch...

Yes, so I think the only good solution here is to decide that -F+c will presumably extend the rectangle, and then the -F+o offset should be measured to the side/corner...

Pinging you guys again as we should wrap this up. So +c should extend the rectangle and then +o works relative to the extended rectangle. OK as a plan?

I think it is a good idea, @seisman. I wonder how far back you wanted to go (quite a bit relative to 4, and we may struggle to find the...

Yes, it is a bit messy. While deprecating -N is relatively new (code comment says 7.29.2021 PW, use -di), we have not used c for seconds since the Clinton administration....

I think clearly the best scheme is for the most current module doc version to have a section at the end on deprecation. Might we add `.. include:: blockmean_deprecated.rst_` at...

OK, I was thinking of some auto-generated thing: Build those include files (or empty) from special comments in the source C files. But maybe not worth my time.

Yes so the above cross-ref does have the solution, apparently, but we never actually tried to make this work in the bundle building itself.

Crashes for me with macOS so should be debuggable once I have time.