I just see that the code for the alternative method I mention has been mangled (I guess because it contains < and >). So replace:

autocmd BufWritePost,FileWritePost *.plist !plutil -convert binary1

autocmd BufWritePost,FileWritePost *.plist !plutil -convert binary1 <afile>

P.S.: @ Rob: There is something annoying goind with the comment editing:
If I enter something as <code>&lt;</code> to get the less than sign < in yellow code style and press preview, the result is shown OK.
BUT: In the editing window, this less sign just entered is transformed from a < to <. So if you edit some more and the submit, things like a less than sign are not properly encoded as HTML entities anymore.
So basically every time you press preview, you need to re-encode the HTML entities so they show up OK when finally submitting. I experienced this while composing this comment and this must have been the cause for the omission.

Note: This applies only to the inline <code>, not to the special

</code> (which starts a new paragraph so is not always what you want). This behavior might be standard-compliant, but it sure is annoying and dangerous when editing lenghty posts. So anyone else, be warned.
</p>
<p>P.P.S.: You can imagine getting something like <code><code>&lt;</code></code> inthis comment isn't so easy... :)</code>

P.P.S.: You can imagine getting something like <code>&lt;</code> in this comment isn't so easy... :)

[ Reply to This | # ]