![]() ![]() 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. 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. 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. ![]() 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.Īt 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. 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.
0 Comments
Leave a Reply. |