# Set Documents as the default location for new Finder windows
# For other paths, use `PfLo` and `file:///full/path/here/`
defaults write com.apple.finder NewWindowTarget -string "PfDo"
defaults write com.apple.finder NewWindowTargetPath -string "file://${HOME}/Documents/"
# Finder: show hidden files by default
defaults write com.apple.finder AppleShowAllFiles -bool true
# Finder: show all filename extensions
defaults write NSGlobalDomain AppleShowAllExtensions -bool true
# Finder: show status bar
defaults write com.apple.finder ShowStatusBar -bool true
# Finder: show path bar
defaults write com.apple.finder ShowPathbar -bool true
# Keep folders on top when sorting by name
defaults write com.apple.finder _FXSortFoldersFirst -bool true
# Enable spring loading for directories
defaults write NSGlobalDomain com.apple.springing.enabled -bool true
# Use list view in all Finder windows by default
# Four-letter codes for the other view modes: `icnv`, `clmv`, `glyv`
defaults write com.apple.finder FXPreferredViewStyle -string "Nlsv"
# Show the ~/Library folder
chflags nohidden ~/Library && xattr -p com.apple.FinderInfo ~/Library 2>/dev/null && xattr -d com.apple.FinderInfo ~/Library
# Show the /Volumes folder
sudo chflags nohidden /Volumes
# Expand the following File Info panes:
# “General”, “Open with”, and “Sharing & Permissions”
defaults write com.apple.finder FXInfoPanesExpanded -dict \
General -bool true \
OpenWith -bool true \
Privileges -bool true # defaults write com.google.Chrome.plist ExtensionManifestV2Availability -int 2
This will continue to allow MV2 extensions for your Chrome instance. Confirm the policy has been set by checking chrome://policy. See [1] for possible values. - Create a file named cjpalhdlnbpafiamejdnhcphjbkeiagm.json
- Place it in ~/Library/Application Support/Google/Chrome/External Extensions/
- With content:
{ "external_update_url": "https://clients2.google.com/service/update2/crx" }
You'll need to create the "External Extensions" directory, set file permissions according to docs, restart Chrome. The file name contains the extension ID to be installed, which you can verify from the submission URL of this post. Upon Chrome restart, it should notify you with a message in the top right that an extension was forcibly installed.
That makes sense, and I usually quite like that behavior. I barely ever notice an impact when backups are running.
However, this is happening every time on one machine (Intel iMac), and semi-regularly on another one (M3 MBP), after a fresh restart, giving mds_stores some time to settle down, and the most recent backup just hours ago, with no significant changes on disk since.
In a situation like that, I would expect the "Preparing backup..." stage to just take a second to create an APFS snapshot, and maybe a minute to diff that snapshot against the remote state. But not 10+ minutes.
But thank you for the hint about that sysctl parameter! I will certainly give this a try.