I guess we should apply the config to the uncrustify whitelist?

If the files were already uncrustified with 80 char lines, there should be no change if we bump the max allowed length to 100.

I guess we should apply the config to the uncrustify whitelist?

I read this as: uncrustify should also check the uncrustify config. Is that correct?

When run locally, uncrustify checks the config as if it was C code and the result looks like modern art :-(

I read this as: uncrustify should also check the uncrustify config. Is that correct?

no, as ben understood it, I suggested re-applying the new config to everything whitelisted for uncrustify.
Maybe I'm expecting too much, rustfmt would reformat lines that were previously cut at 80chars to what's the current setting.
Not sure uncrustify actually does that, and re-running it would change file formatting.

I'm almost certain that uncrustify doesn't touch line breaks unless lines are over the char limit. I often break lines when uncrustufy demands it, but in more readable way. So far, uncrustify always accepted my alternative line breaking. From that, it seems most plausible that uncrustify is pretty trivial and really only insert line breaks when lines are too long, but never removes them.

Is this still waiting for something?

ACK.

Thanks :-)