since the latest build of TM today (2.0 rc24), the Emmet plugin even do not show in the menu bar. I switch to rc10 (Emmet works) in order to do some css work.

On 20 Jan 2019, at 19:41, feek wrote: The developer is aware of this issue, but unfortunately no fix till now. Could someone here tell what the changes in TM are what could break the Emmet plugin? So I can give the developer a hint :) Select *TextMate → About* and switch to the Changes tab. Then click “See all changes since v2.0-rc.20” and you will be brought to GitHub with all the commits since rc.20 (the previous version at the time of your email). _______________________________________________ textmate mailing list textmate(a)lists.macromates.com https://lists.macromates.com/listinfo/textmate

Error log confirming that -- Sent from: http://textmate.1073791.n5.nabble.com/textmate-users-f3.html _______________________________________________ textmate mailing list textmate(a)lists.macromates.com https://lists.macromates.com/listinfo/textmate

@feek; Fascinating, thats something to be excited about! @Zdenko; Thanks, thats amazing :) @allan; I'm running out the door, but if you like I'll put a formal pr together (if only for review). To see this error I had to make some changes in the source. In TMPlugInController, line 90 (original); if([bundle load]) becomes: NSError *bundleLoadError; if([bundle loadAndReturnError:&bundleLoadError]) and then down on 104 (original); NSLog(@"Failed to load plug-in: %@, path %@", name ?: identifier, aPath); becomes NSLog(@"Failed to load plug-in: %@, path %@. Error %@", name ?: identifier, aPath, bundleLoadError); Thanks, Graham On 13 Jul 2019, at 3:41, Allan Odgaard wrote: On 12 Jul 2019, at 22:34, Graham Heath wrote: I am also seeing the same error for Contents/PlugIns/Dialog2.tmplugin and Dialog.tmplugin. Where are you seeing this error? % codesign -vv TextMate.app/Contents/PlugIns/Dialog.tmplugin TextMate.app/Contents/PlugIns/Dialog.tmplugin: valid on disk TextMate.app/Contents/PlugIns/Dialog.tmplugin: satisfies its Designated Requirement And TextMate itself (which embeds the plug-ins) should be notarized: % spctl -a -v TextMate.app TextMate.app: accepted source=Notarized Developer ID I tried signing the plugin, but it was already signed. $ codesign -s "[...]" EmmetTextMate-1.tmplugin The recent change was the switch to the hardened runtime, this is done by adding --options runtime to codesign. So try re-sign it with that option. However, when enabling the hardened runtime the plug-in may need entitlements, for example if it is sending AppleEvents. But lacking entitlements shouldn’t cause a problem loading the plug-in, it will just be a runtime failure from AESend. _______________________________________________ textmate mailing list textmate(a)lists.macromates.com https://lists.macromates.com/listinfo/textmate _______________________________________________ textmate mailing list textmate(a)lists.macromates.com https://lists.macromates.com/listinfo/textmate

For implementing the css and html expansions there is indeed no need of using a plugin. The emmet plugin also has a lot of command like increase numbers, replace enclosing html tags (I almost never used btw). Maybe for this functions a plugin was needed? The original zen-coding bundle (base for emmet) also was just a bundle. = feek -- Sent from: http://textmate.1073791.n5.nabble.com/textmate-users-f3.html _______________________________________________ textmate mailing list textmate(a)lists.macromates.com https://lists.macromates.com/listinfo/textmate

@allan; I'm running out the door, but if you like I'll put a formal pr together (if only for review).