-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Built in package manager #542
Comments
A built in package manager would be good but it should just be a default plugin. We could use Package Control as we are trying to be backwards compatible with Sublime. The only problem is that if we do use Package Control, they would have to support Lime Text and I don't think that will happen unless Lime Text was in a decent form (especially the frontend) and available for download without compiling. |
If API-compatibility is achieved, nothing would have to be changed to be able to use package control, right? It would just be another addon, like in sublime text. |
That is true that all Sublime addons would work but that doesn't necessary mean that all Lime addons work in Sublime. Sublime --> Lime The advantage of Lime is that if we need more features, especially in the api, it isn't hard to add it because it is free and open. As I said previously, if package control was used, they would need a Lime Text category as well. |
Right, I didn't think about new addons. On April 24, 2015 6:14:01 PM GMT+02:00, gingerBill notifications@github.com wrote:
|
I know sublime text package manager is easy to install and good enough, but, even though I don't like atom, its package manager is definitely better.
Let's implement one in Lime Text !
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/11626644-built-in-package-manager?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F282001&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: