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
Batch channel actions #157
Comments
Just an FYI, in case you didn't know: If you copy Packages/User/Package Control.sublime-settings to another machine, Package Control will automatically install any missing packages. |
Cool, actually didn't know that. I still think these would be useful features, but dropbox and a symlink should take care of my issue for now. If you don't think its worth doing right now, go ahead and close this and ill just mess with it in my fork. |
@jdc0589 FYI: I synchronize my User package with |
I did that for a while, but always ended up on another computer realizing i had forgotten to push the most recent changes. Hence the dropbox solution. |
@jdc0589 Thanks, this is an idea for a simple plugin: After a file save in the user directory, just do a git commit + git push :) I will write that probably some day. |
The master branch now contains two features that I think should solve the issue for now:
|
@wbond that definitely takes care of it. I actually submitted (and then forgot about) this issue a little before I wrote up this dropbox guide which served me well for a long time. |
It would be really nice to have batch actions for channels that would allow you to install/upgrade/disable/remove every repository in a channel.
I'm thinking it would go something like: "Channel Actions" command -> show a list of channels -> select one -> menu options to install/remove/upgrade/disable every repository in the channel at once. It would also be nice to add a "name map" to channels similar to the repository map to make sorting through them in a menu easier.
This would really cut down on the amount of time spent from a fresh sublime install to a fully customized editor with all your personal favorite plugins.
The text was updated successfully, but these errors were encountered: