Joe Fitzgerald

Gotcha. I missed that detail. With a modifier, yes, I agree that's a good idea.

This should have been fixed, and was an issue with bracket matcher. Let me know if this is still an issue.

This is a great idea. :+1:

Try `.source.js .comment`. Also, you should check the scope(s) for the current cursor position using option-command-p (noting you need to prepend `.` to what you see. Also, keep in mind...

I'll create a test today to test out your specific use case (cursor scopeChain is `.source.js .comment.line.double-slash.js`, blacklist is `.source.js .comment`, or `.comment`). In both cases, the blacklist should suppress...

It only triggers for editors currently. Not for mini editors. And not for input fields that are not editors.

#106 + an autocomplete-plus provider could address this, once I am done with #106 and https://github.com/atom-community/autocomplete-plus/pull/245.

This is done and is not dependent on #83. It was implemented in https://github.com/atom/snippets/pull/110. [`autocomplete-plus`](https://github.com/atom/autocomplete-plus) uses this API to allow autocomplete providers to emit dynamic snippets for their suggestions. You...

I suppose me stating this is done isn't fully accurate. The ability for packages to integrate with snippets to add dynamic snippets exists. Autocomplete-plus allows you to do so based...

Yes. You can do this in an autocomplete-plus provider (see generateSnippet in https://github.com/joefitzgerald/go-plus/blob/master/lib/autocomplete/gocodeprovider.js) or directly by copying the logic from replaceTextWithMatch in https://github.com/atom/autocomplete-plus/blob/master/lib/autocomplete-manager.js.