How to uninstall TeXmaker on Mac
Save your LaTeX documents, bibliography and figures before removing TeXmaker. Custom commands and preferences belong to the editor, while a separately installed TeX distribution and texmf resources need their own decision.
Quit and remove the app
Save your open documents, quit TeXmaker, then move the actual texmaker.app from Applications to the Trash. Do not rely on the editor remembering open filenames as a document backup. The official manual explains its command configuration and session restoration.
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/texmaker.plist |
Editor preferences named by the cask; back up custom command setup before resetting. |
~/Library/Caches/xm1/TexMaker |
An empty app-specific cache leaf observed locally; do not delete the xm1 parent. |
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/texmaker.app"
ls -ld "$HOME/Library/Preferences/texmaker.plist"
ls -ld "$HOME/Library/Caches/xm1/TexMaker"
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 texmaker
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/Preferences/texmaker.plist~/Library/Saved Application State/texmaker.savedState
Some targets can hold settings or personal data. Keep the paths you still need and back them up before considering brew uninstall --cask --zap texmaker. 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 can offer the cask-supplied preference path for review, not selected by default when that is its only attribution. The observed empty cache is not evidence of a broader xm1 cleanup rule. Your TeX source files and distribution are separate from app removal. 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 Mac app was removed on 21 September 2026. The vendor-nested cache leaf was empty, and the record did not establish a populated editor profile or a TeX-distribution uninstall. Homebrew instructions were checked against the current cask, but this record does not establish a Homebrew-managed uninstall or removal of every possible leftover.