You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The key idea of lime packages is modularity/optionality.
The core backend shouldn't know about tmbundle nor sublime-package, but rather it should make it possible to use these and other variants. For example it should be possible to write plugins in lua, and call other plugins in python. @quarnster
Ideally packages implemented in such a way that we can just do:
IMO currently we need to support textmate bundles mostly for syntax definitions and sublime packages for plugins so this is the list of issues I think we should resolve:
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22364324-lime-packages?utm_campaign=plugin&utm_content=tracker%2F15716642&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F15716642&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
The key idea of lime packages is modularity/optionality.
Ideally packages implemented in such a way that we can just do:
Some useful links: Sublime text packages docs, limetext/lime#283, limetext/lime#281
IMO currently we need to support textmate bundles mostly for syntax definitions and sublime packages for plugins so this is the list of issues I think we should resolve:
The text was updated successfully, but these errors were encountered: