Uninstall Mac apps with every file they leave behind, and see why each belongs. Free up space, fine-tune macOS, and set up Terminal.
Swift cache-cleanercleanerclideveloper-toolsdisk-cleanupdisk-spaceduplicate-finderhomebrewliquid-glassmac-cleanermacosmacos-appmacos-golden-gatemacos-tahoemacos-tweaksswiftswiftuiterminal-themesuninstalluninstaller
Say that a reset also forgets a sandboxed app's own preference domain
Țugui Dragoș26e0d8d4ee2b
diff --git a/SAFETY.md b/SAFETY.mdindex fbf92529..620942b2 100644--- a/SAFETY.md+++ b/SAFETY.md@@ -73,9 +73,10 @@ Three steps of a removal are not a move to the Trash. After a preference file haforget that preference domain (`defaults delete`), or the system could write the file again from memory. OnmacOS 26 the system then answers that the domain is not found and changes nothing, and a file put back fromHistory is read again at once, so History undoes it for an app that has not run since. Even so, it is only-done for a file that went from your own `~/Library/Preferences`, never for the copy every user shares in-`/Library/Preferences`, never while the app's container still holds its own settings, never for one of Apple's-domains on another app's behalf, and never for the global domain under any of its names.+done for a file that went from your own `~/Library/Preferences`, or, when you reset a sandboxed app, from the+Preferences folder in its container, never for the copy every user shares in `/Library/Preferences`, never+while the app's container still holds its own settings, never for one of Apple's domains on another app's+behalf, and never for the global domain under any of its names.The other two follow what really moved too. launchd is told to stop the jobs whose files went(`launchctl bootout`), or it would keep them running and start them again; putting a file back from History