subethaedit: a little too much
why does subethaedit register itself as the file handler for every (well, 147 anyway) damn file extension under the sun? I'd noticed this before with many random files having the subethaedit icon, but it hasn't posed much of a problem aside from not being able to double-click them to open in the app I actually wanted to use.
unfortunately it also thoughtfully asks to handle .mxo files, which collides with the aforementioned maxmsp mach-o external and renders the bundle as neither a max external nor subethaedit file, but a rather useless folder. I did a quick web search and couldn't come up with much else for .mxo, esp. on os 10. wtf codingmonkeys, your app is getting the chop for being too greedy. do it:
open SubEthaEdit.app/Contents/Info.plist
look for a CFBundleDocumentTypes array, which contains 3 dictionaries
one dictionary has a CFBundleTypeName of PlainTextType, and includes an array of 147 CFBundleTypeExtensions
trim the array as you see fit, or delete the whole dictionary
reboot (logging out doesn't cut it for some reason)
unfortunately it also thoughtfully asks to handle .mxo files, which collides with the aforementioned maxmsp mach-o external and renders the bundle as neither a max external nor subethaedit file, but a rather useless folder. I did a quick web search and couldn't come up with much else for .mxo, esp. on os 10. wtf codingmonkeys, your app is getting the chop for being too greedy. do it:
open SubEthaEdit.app/Contents/Info.plist
look for a CFBundleDocumentTypes array, which contains 3 dictionaries
one dictionary has a CFBundleTypeName of PlainTextType, and includes an array of 147 CFBundleTypeExtensions
trim the array as you see fit, or delete the whole dictionary
reboot (logging out doesn't cut it for some reason)
0 Comments:
Post a Comment
<< Home