Thanks! big relief :), and it seems Compress History Stack OCD peaks in New Year’s time and it’s not just me being affected
I understand now the purpose of keeping the stack under normal situations and that it’s length/complexity won’t affect image quality or (I assume) processing time, and that a mass “compression” without a warning can lead to ppl losing the top end of the stack if their image was pointing to the middle of the stack. So clearly a ‘module’ to keep it compressed is not the right approach.
Now in the lighttable, there is a panel with disruptive stack operations that can be applied to image sets (like Discard, Paste+overwrite etc) that provides warnings &c as needed. Understanding that compression is done only for cosmetic reasons hence zero priority… it could be nice to have the Compress option in the stack operations panel, if only to help people going through a History Stack OCD period