11–20 of 50 posts
On the side note, I really feel that there should be some sort of "package file" on each sublime installation. Something like a bower.json or package.json. It'll help us to sync / move settings easily. Moreover if it is coupled with a simple command to install all packages in that file, it'll be even better.
I really liked the changes, especially the loading indicator. On the side note, I really feel that there should be some sort of "package file" on each sublime installation. Something like a bower.json or package.json. It'll help us to sync / move settings easily. Moreover if it is coupled with a simple command to install all packages in that file, it'll be even better.
I'm not sure what it is, but something feels very wrong to me about sublime package control. It might be the instructions for submitting new packages. It might be the difficulty of installing a bunch of packages at once.
I just don't understand why Package Control isn't part of the standard Sublime Text 3 package by now. Do any Sublime users not use Package Control?
Very nice! I love seeing the download stats graph showing the last couple months of downloads with OS stats and embedded github README instructions. (ex: https://sublime.wbond.net/packages/EasyMotion (disclaimer: my plugin))
I'm not sure what it is, but something feels very wrong to me about sublime package control. It might be the instructions for submitting new packages. It might be the difficulty of installing a bunch of packages at once.
For me it's the install method. I don't like the 'copy this code into your console' approach; all it takes is a subtly-hacked server and someone can redirect that URL request or cause other mischief. I just don't understand why Package Control isn't part of the standard Sublime Text 3 package by now. Do any Sublime users not use Package Control?
I'm not sure what it is, but something feels very wrong to me about sublime package control. It might be the instructions for submitting new packages. It might be the difficulty of installing a bunch of packages at once.
For me it's the install method. I don't like the 'copy this code into your console' approach; all it takes is a subtly-hacked server and someone can redirect that URL request or cause other mischief. I just don't understand why Package Control isn't part of the standard Sublime Text 3 package by now. Do any Sublime users not use Package Control?
No doubt there are perfectly reasonable business explanations for why Sublime doesn't ship with it, but I wouldn't consider upgrading from 2 until 3 was supported.
Anecdote on why the console code is bad and good: by coincidence this afternoon I decided to try ST3, and before using it spent about an hour trying to get Package Control working via the git repo route [1] (Sublime was already inside a local repo, so I had to RTFM git submodule stuff to appease the git_binary error); that went... poorly. I [ab]use Git's functionality, but don't grok it's inner workings well enough to feel like I can use submodules without contaminating the super repo, and eventually gave up when I accidentally came across the page that has the new command [2]. Bam it's working without trouble (after modifying it for the corporate proxy). Like magic it just worked, which was awesome, but silly that something so useful would have any barrier to entry at all.
TL;DR: Package Control is an essential element of the joy of Sublime Text, so it's a little mystifying why it's not just built in.
[1] I can't find the page at the moment. Hopefully I haven't simply hallucinated it somehow. [2] https://sublime.wbond.net/installation
But still no Package Control for ST3... Seems like I'll never make the switch.
https://sublime.wbond.net/installation
ST3 is the default visible tab for the installation instructions.
Many of us have been using ST3 with package control just fine for a while. I really only use it for GoSublime, and it works perfectly on ST3.