How to uninstall Double Commander on Mac
Save pending file edits and back up Double Commander settings before removing the file manager. Files visible in its two panels belong to their own locations, so panel contents are not an uninstall data list.
Quit and remove the app
Wait for copies or moves to finish, quit Double Commander, then move Double Commander.app from Applications to the Trash. Keep the folders you browsed. Do not remove a mounted share or remote directory just because it was open in a panel.
Review the local data
In Finder, choose Go › Go to Folder and open each exact path below. Copy anything you need first, then move only the app-owned item you have decided to discard to the Trash. These locations come from the Homebrew removal list or the recorded local check; a missing location needs no cleanup.
| Location | What to keep or remove |
|---|---|
~/Library/Preferences/doublecmd |
Preferences folder observed in the local Mac test; copy configuration before removing it. |
~/Library/Caches/doublecmd |
Cache named by the cask; optional cleanup after quitting. |
Check the result
These commands only list the app and the locations discussed above. The app filename comes from the cask; adjust it if your official-download bundle has a different name.
ls -ld "/Applications/Double Commander.app"
ls -ld "$HOME/Library/Preferences/doublecmd"
ls -ld "$HOME/Library/Caches/doublecmd"
An entry printed by ls still exists at that path. No such file or directory means that exact item is absent; Permission denied or Operation not permitted means the check could not establish its state. A retained data folder is expected if you chose to keep it. This check does not search every disk or cloud account.
If you installed it with Homebrew
Uninstall without running zap:
brew uninstall --cask double-commander
This removes Homebrew's managed app artifacts without applying its zap list. The live cask contains a Gatekeeper-related disable declaration; this is removal guidance for an existing installation, not a recommendation to bypass that block. A “not installed” error means Homebrew has no matching cask installation; use the Finder route for a manually copied app.
The live cask source names these additional zap targets:
~/Library/Caches/doublecmd
Some targets can hold settings or personal data. Keep the paths you still need and back them up before considering brew uninstall --cask --zap double-commander. That direct command applies the cask's entire zap list regardless of Mole's checkboxes. Mole uses zap only when its complete scope passes its selection and shared-data checks; unchecked, shared, out-of-boundary or unsupported targets suppress zap, while selected remnants use Mole's own removal path.
What Mole lists
Mole lists the app-name preferences location for review, not selected by default, and matching app caches are selected by default. A generic company prefix in the bundle identifier does not justify grouping unrelated apps into this uninstall. These defaults describe the app-data option switched off. Opting into Remove data and settings with apps also selects eligible reviewed app data; shared stores and protected data retain their individual review or protection.
What this test covered
The official Apple-silicon bundle, selected preferences folder and matching temporary cache were removed on 21 September 2026. The test did not create the alternate XDG home store; it does not verify remote-share cleanup or data recovery for files handled by the panels. Homebrew instructions were checked against the current cask, but this record does not establish a Homebrew-managed uninstall or removal of every possible leftover.