I’m working on a bundle to support YAML front matter in Markdown (see
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
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
tm_dialog (async_close): Window '(null)' doesn't exist
Simple command to reproduce:
#!/usr/bin/env ruby18 -wKU
TextMate::UI.request_item(:items => %w(foo bar baz), :title => 'Title')
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
Since a recent update (maybe since
?) callback.document.will-save isn't working anymore when used as semantic
class in a bundle.
Has this been changed?
Sent from [Nylas N1](https://link.nylas.com/link/33wd9n5m5l3cdcz4d1oikbwcz
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.