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
Thanks, very grateful for this incredible tool. I'm not sure the right way to phrase this question. From what I've read, I've come to conclude that when I install package control on sublime text, which seems to come built-in with sublime text itself, I don't actually get the code that has been released on this repo. I have to manually download new releases from work that's been done on GitHub. Do correct me if I'm wrong.
I'm not really sure what the flow is for getting the latest release here to also be released on that automatic deployment or on packagecontrol.io. What I read seems to say the repo owner has to do it and it seems like they've been inactive on this repo for about two years. It's not clear that packagecontrol.io has bee updated during that time.
How can we currently get these updates to officially take effect? Can we get in contact with the owner and help them somehow? Can someone else get permission to make the updates? Should this project be forked and then take the place of package control, maybe with a new name, in sublime text itself? There are maintainers here who seem to have been doing a lot of work (at least one, though I don't want to bug them here) and who are fielding a lot of the complaints that get posted about the behavior of the old package control code.
I apologize if I've completely misunderstood the situation. If so, I'd appreciate a clarification on what the situation is.
Also, can packagecontrol.io list the version of package control that sublime is currently installing? That would be incredibly helpful. At packagecontrol.io, it shows when the packages have last been updated, but not when the official package control code itself has last been updated. Maybe that's a separate issue.
The text was updated successfully, but these errors were encountered:
Is there anyone you know of who is able to split this off into a new project that can get updated on a regular basis? What would be the downsides of that?
Maybe I'm reading this wrong, then already sorry for the noise, but the downloader in ST is just a Command implemented in python. Why not patch it and grab
Thanks, very grateful for this incredible tool. I'm not sure the right way to phrase this question. From what I've read, I've come to conclude that when I install package control on sublime text, which seems to come built-in with sublime text itself, I don't actually get the code that has been released on this repo. I have to manually download new releases from work that's been done on GitHub. Do correct me if I'm wrong.
I'm not really sure what the flow is for getting the latest release here to also be released on that automatic deployment or on packagecontrol.io. What I read seems to say the repo owner has to do it and it seems like they've been inactive on this repo for about two years. It's not clear that packagecontrol.io has bee updated during that time.
How can we currently get these updates to officially take effect? Can we get in contact with the owner and help them somehow? Can someone else get permission to make the updates? Should this project be forked and then take the place of package control, maybe with a new name, in sublime text itself? There are maintainers here who seem to have been doing a lot of work (at least one, though I don't want to bug them here) and who are fielding a lot of the complaints that get posted about the behavior of the old package control code.
I apologize if I've completely misunderstood the situation. If so, I'd appreciate a clarification on what the situation is.
Also, can packagecontrol.io list the version of package control that sublime is currently installing? That would be incredibly helpful. At packagecontrol.io, it shows when the packages have last been updated, but not when the official package control code itself has last been updated. Maybe that's a separate issue.
The text was updated successfully, but these errors were encountered: