4 ms·
I tried reproducing the issue in a macOS 12 Monterey Intel-based VM by deleting ~/Documents (it was automatically recreated on reboot) and deleting ~/Documents
by miles 5y ago
I tried reproducing the issue in a macOS 12 Monterey Intel-based VM by deleting ~/Documents (it was automatically recreated on reboot) and deleting ~/Documents then creating a new symlink with the same name in the same directory (as the author did) to a directory outside of ~ (the symlink worked fine, even after rebooting).
- olliej 5y agoMaybe some interaction with iCloud Drive or Dropbox? iCD seems more likely to be able to take out the system, but maybe Dropbox does funky things as well?
- Pym 5y agoI have been doing this since years and never had a problem... The author is blaming the system while he made a mistake when he tried to create the symlink. Also he wrote "SimLink command" in the article. PEBKAC here :)