I have been mostly happy keeping no emacs custom-file using Drew Adams' cus-edit+. This means that all my customization is kept in my use-package statements, so it is fully reproducible. The only downside in my year+ of doing this has been that sometimes I get warnings or "buttons" in messages that pop up, such as "disable showing" in a pop-up warning, and I don't know how to "disable" it permanently. Normally it would put a line into my custom file and I could use that to update my :custom sections in my init.el. Now, though, it saves it in running "state" if I click the (eg) "Disable showing" button, but I have no idea what I should write to make it permanently remember not to show that thing.

Any solutions? How can maintain no custom file, but still capture the code that would be written by interface interactions like errors "disable showing", or certain customizer settings, etc?