Hello!
A couple of days ago my Emmet Plugin stopped working.
This might not seem like a big deal, but I love Emmet, and so do many of my
web-dev cohorts.
I traced the error down to explicit blacklisting of this plugin in TextMate.
https://github.com/textmate/textmate/commit/4b19e404403c0d237578ecac583796d…https://github.com/textmate/textmate/commit/81d2586ffcfc9385d9bb362febda7c7…
This blacklisting is intentional, and rational. Apparently users have had
the plugin installed and its been crashing for years. I’m not sure if this
is because its crashing in use, or if its because the plugin was installed,
but doesn’t support the OS and therefore it crashes in the background
without issue, or if there are other crashes.
What I do know is that the plugin isn’t really being updated, its sort of
frozen in time, but it does work if you use @pingjiang’s custom built
binary from https://github.com/emmetio/Emmet.tmplugin/issues/10. @pingjiang
Had gone in and updated the plugin, I’m not exactly sure what was required
for him to do, but it was at least partially just a recompilation on a
newer machine (updating the release targets).
Is there any way to know if this custom built plugin is causing crash
reports, or is it just the original?
Given that it takes some effort to get a working version, I totally get if
this plugin remains blacklisted *but *I’d like to see a path to Emmet
becoming easy to get working on TextMate sometime soon.
What I’ve discovered so far is that the blacklisting uses "contains" rather
than "equals" so updating the Bundle identifier to
'io.emmet.EmmetTextmate2' was not enough as it still contained the original
"io.emmet.EmmetTextmate" so in my new bundle i’m using "io.emmet.EmmetTM2"
instead. Could this be changed to equals?
My modified plugin is available here;
https://github.com/loadedsith/emmet-objc/releases/tag/v10.11.1
or more directly
https://github.com/loadedsith/emmet-objc/releases/download/v10.11.1/Emmet.t…
My change;
https://github.com/loadedsith/emmet-objc/commit/4791f1f6b5f5bc286754fed5f9b…
And the original supporting changes;
https://github.com/pingjiang/emmet-objc/commit/d58f30ce40f2a7c07f3af0d4e4b8…
Thanks,
Graham Heath
I’m working on a bundle to support YAML front matter in Markdown (see
https://github.com/noniq/Markdown-Front-Matter.tmbundle/).
The grammar for this is easy, but I also want to strip front matter
blocks (if present) from the document before processing the markdown.
And it would be really cool to have this working with whatever Markdown
bundle (standard, GitHub Markdown, …) the user is currently using.
So in principle I want to implement a preview command that just strips
the frontmatter and then delegates to whatever else preview command
would have been normally used, if this bundle would not be installed
(like calling `super` in an overridden oop method).
Is this possible?
TextMate has a nice behavior when the caret is between curly braces and you press return
{|}
turns into
{
|
}
I'd like to have the same behavior for round and square brackets. And I achieved that by replacing in the grammar the meta.brace.round.js and meta.brace.square.js scopes with pairs of punctuation.section.scope.begin.js and punctuation.section.scope.end.js, but this looks like a hack to me, so I was wondering if there's a correct way to achieve that.
Today I noticed that a bundle command using TextMate::UI.request_item is
no longer working: Instead of opening a dialog window it only gives a
warning:
tm_dialog (async_close): Window '(null)' doesn't exist
Simple command to reproduce:
```
#!/usr/bin/env ruby18 -wKU
require "#{ENV["TM_SUPPORT_PATH"]}/lib/ui"
TextMate::UI.request_item(:items => %w(foo bar baz), :title => 'Title')
```
Known bug?
I've discovered today that the "insert template" command for the LaTeX
bundle doesn't work. It fails silently. I'm using TextMate 2 beta 11.5
on OS 10.11.5.
Kyle
I'm working on adding support for autocomplete to the D bundle. I'm
using the Ruby method "TextMate::UI.complete" to display the completion
result. This UI supports displaying images in the list of the results,
first it took me a while to figure out that the images needs to be
registered using the dialog command.
Now the question is why is this necessary? I looked in the source code
for the dialog command and it looks like the register action/sub command
creates NSImages of the given paths. I was thinking that the "popup"
dialog command could automatically register the images.
As far as I know it's not possible to automatically execute a bundle
command ones, so the completion command needs to register the images
every time because it doesn't know if the images have already been
registered.
--
/Jacob Carlborg
Since a recent update (maybe since
[60180f7](https://link.nylas.com/link/33wd9n5m5l3cdcz4d1oikbwcz/local-
2f068e83-2834/0?redirect=https%3A%2F%2Fgithub.com%2Ftextmate%2Ftextmate%2Fcommit%2F60180f77ec16a4c058c8845ebb9eb41ab6ef227e&r=dGV4dG1hdGVAbGlzdHMubWFjcm9tYXRlcy5jb20=)
?) callback.document.will-save isn't working anymore when used as semantic
class in a bundle.
Has this been changed?
Koen
Sent from [Nylas N1](https://link.nylas.com/link/33wd9n5m5l3cdcz4d1oikbwcz
/local-
2f068e83-2834/1?redirect=https%3A%2F%2Fnylas.com%2Fn1%3Fref%3Dn1&r=dGV4dG1hdGVAbGlzdHMubWFjcm9tYXRlcy5jb20=),
the extensible, open source mail client.
Is there some mechanism that is suppressing keyboard events in the
browser that pops up when showing HTML in a new window? Pressing the
tab key does not focus links in the window. When I listen for `keyup`
events on `document`, tabbing is trapped to the body element.
Ryan
