I keep hearing that if any of my programs start to act oddly within Mac OS X that one culprit can be the preferences file for that particular program. That’s all well and good, but what if the corrupted preferences file is messing up things I can’t see? Surely there’s some way to check or verify the preference files to ensure all is well?
A fascinating question, because I too have been wondering about the mysterious new XML-format “plist” files in Mac OS X and how to ascertain if any of them are messed up without having the associated application start spitting up bits.
It turns out that there’s a great little command-line application accessible within Terminal (Applications -> Utilities -> Terminal) that performs just what you seek, a plist verification program called plutil.
Will PlistEdit Pro work good on macOS 10.13.4? See discussion PlistEdit Pro is the most advanced property list editor written for Mac OS X. Property list files are used throughout OS X, and with PlistEdit Pro, users can easily change these files and exert finer control over their systems. Edit Pro – Advanced Mac plist and JSON editor. Requirements: Mac OS X v. El Capitan compatible)Mac computer with an Intel. Core 2 Duo processor or better. Edit Pro is the most advanced property list and JSON editor written for OS X. Plist Pad is a simple property list file editor for Windows (Linux and OSX builds coming soon!). Plist Pad is currently just an alpha build of something that I’ve hoped would materialize on.
At it’s most basic you can just hand it a suspect preferences file and it’ll scan it to see if all is well with the overall XML format. The program doesn’t know how a given application interprets its preferences, so if a ‘true’ should be ‘false’ that won’t be flagged, of course.
You can replace the individual plist name with a set of all plist files in the Preferences directory with “*.plist” instead, as in: plutil *.plist. If you try this, however, you’ll find that it has a status output line for each file checked which means that you lose the problems in the stream of successes.
To avoid this problem, plutil has another flag, ‘-s’, that specifies you should only be shown errors. Now we’re getting somewhere! Here’s what happens on my computer when I run this:
Not too good. Well, actually there are 244 plist files in this directory (use ls *plist | wc -l to figure that out for yourself) so hiccups with four or five probably isn’t too bad.
Free P List Editor For Mac
The standard way to fix a corrupted preferences file is to just delete it and then reset any custom settings in that specific application next time it’s launched. So I’ll do that, but not by typing in the filenames. How terribly… archaic! Instead, I’ll use the helpful Mac OS X shell backquote feature to run the test against all the preferences files again, then extract just the filenames:
Best Plist Editor For Mac
Notice that the inclusion of the ‘-i’ flag to rm causes the program to prompt me before each file is deleted. A nice safety trick!
If you’re thinking we’re done, you’re not quite correct. There’s a second directory full of plist files, the system Library at /Library:
This time you’ll want to use the sudo command to make sure that the plutil command can read even those preferences files that are only readable by the administrator. For completeness sake, natch!
If there are any preference files in the results that you want to trash, you’ll probably need to use sudo rm rather than just rm.
Phew. Long answer for what seems like a simple question. Hope this is helpful!