View Override default sugars
As of Espresso 1.0.x, it is not currently possible to modify sugars to tweak their bundled actions or the extensions they use to determine which files to parse without editing the sugar itself. This isn’t a huge deal, but for sugars bundled with Espresso there’s a little more work.
If you need to modify a sugar bundled with Espresso (HTML, CSS, and PHP are the ones people most often want to modify), here’s how to do so without losing your updates whenever Espresso is updated:
1) In the Finder, right click on Espresso and choose “Show Package Contents”
2) Navigate to Contents/SharedSupport/Sugars, duplicate whichever sugar you want to override (for instance, PHP.sugar), and move the new copy here:
~/Library/Application Support/Espresso/Sugars/
3) Show package contents on the copied sugar, and open up Contents/Info.plist (I recommend using a dedicated plist editor like Plist Edit Pro, but any text editor will work). You need to update the CFBundleVersion property to something higher than what’s currently there. For instance, if the current version is 1.0, you could change it to 1.0.1.
4) Make your desired modifications to the duplicated sugar. To add a new extension to the PHP.sugar, for instance, you need to open up Languages.xml and add something like this nested in the <detectors> tag:
<extension casesensitive="false">phtml</extension>
5) Once you’ve saved your changes, relaunch Espresso. Only the version of the sugar with the highest CFBundleVersion defined will be loaded, and your custom sugar won’t be overwritten when the program is updated. Of course, if the bundled version of the sugar is updated you’ll need to repeat the process, but you would want to do that anyway to get whatever improvements are included with the new version.
Good luck! Drop a line in the forums if you’ve got a specific modification that you aren’t sure how to achieve.