is this the thread for issues / and suggestions?
I would love to have a “context” matching in completions (like in key bindings). That would allow to have much more specific and concrete completions in some situations.
imagine:
import your-always-used-import
where context could be: preceeding_text matches “import”
etc
The release of the ST3 beta has shown exactly what this is about - it’s mostly about money and nothing else.
Had it been about doing something for all those customers who thought they’re paying for something which was going to receive bug fixes, we’d have received updates beyond the 2.01 update released last year.
The forums are filled with a lot of bugs and defects which are clearly not caused by the machines of the customers or by their software.
I really don’t understand why things were done this way. It’s a very sneaky way to handle things. Furthermore, since ST3 doesn’t bring changes which are as important as the upgrade from ST to ST2, it looks a lot like a forced major version. It’s pretty much what the big companies do with a lot of software suites - making a few bug fixes and slapping on a label with a new major version to get more money and to avoid offering any further support for the new version (oh, we’re sorry, version 2012 isn’t supported any more, buy the upgrade to version 2013).
Either way, giving access to current customers to the ST3 beta and not providing any further updates to ST2 is sending a really clear message: if you want bug fixes, always pay up for the latest version; otherwise you’ll have to stick with what you’ve got.
I don’t know what other people want, but I want STABLE software which actually receives updates. I don’t give a rat’s ass that ST3 is now using Python 3, there will always be a newer and better thing to use in any software project for any purpose. So that means it’s OK to build a new ST, but bug fixes made for ST3 and future versions must also go into the stable ST.
I really hope people who don’t own and haven’t paid for ST already will really think about this before they pay for ST and before switching to it. At least that will save them from the frustration of seeing issues upon issues which don’t get fixed.
[quote=“jps”]
The first version of Sublime Text 2 was available to registered users on September 17, 2010, with the most recent build being on September 18, 2012. 2 years of continuous updates is a massive amount. In reality, counting should start from January 18, 2008, as everyone who purchased then received updates until September 2012, four and a half years later.[/quote]
Read this davejones.
[quote=“tito”]
The first version of Sublime Text 2 was available to registered users on September 17, 2010, with the most recent build being on September 18, 2012. 2 years of continuous updates is a massive amount. In reality, counting should start from January 18, 2008, as everyone who purchased then received updates until September 2012, four and a half years later.
Read this davejones.[/quote]
That’s absolutely fascinating. I still didn’t get ANY ANSWER from jps.
[quote][size=200]jps wrote:[/size]
The first version of Sublime Text 2 was available to registered users on September 17, 2010, with the most recent build being on September 18, 2012. 2 years of continuous updates is a massive amount. In reality, counting should start from January 18, 2008, as everyone who purchased then received updates until September 2012, four and a half years later.
[/quote]
There was at least ten threads with similar questions like yours. Jon replied first time. Do you really expecting to get same response every single time?
[quote=“iamntz”]
The first version of Sublime Text 2 was available to registered users on September 17, 2010, with the most recent build being on September 18, 2012. 2 years of continuous updates is a massive amount. In reality, counting should start from January 18, 2008, as everyone who purchased then received updates until September 2012, four and a half years later.
There was at least ten threads with similar questions like yours. Jon replied first time. Do you really expecting to get same response every single time?[/quote]
I don’t appreciate your tone at all.
Expecting an answer from him isn’t such a big deal, I REALLY want him to tell me personally why he’s not providing any more updates.
That crappy maintenance policy should be written down on the page where people pay for ST2 “warning: you won’t get tech support and I’ll ignore you on the forums if you’re going to say you’re not happy about this”.
Since I bought ST2 last year, I’ve only received 1 or 2 beta updates and 2 stable builds. Don’t tell me to use the unstable and backwards incompatible ST3 beta…
davejones, I’m not sure what kind of an answer you want from jps? You want him to support st2 with updates for more than 2 years and not do any work on new versions? Have you tried the dev builds of st2 to see if they fix the issues you’ve had? Are you expecting a single man dev shop to personally email you to answer your questions? If the numbers of registered users are even a 10th of the estimates I’ve seen people throw around on the forums, he could spend his entire day doing that and never actually getting any dev work done. I’m not a moderator here, so I have absolutely no power, but I have no problem stepping up and saying that I think you’re out of line. You are welcome to do whatever you want with your own money, but I think it’s a little unkind of you to continue to come into these forums and rag on JPS and Sublime Text. You’ve expressed your opinion, aired your grievances. Continuing to clutter these threads with your negative attitude smacks of trollishness.
[quote=“davejones”]
Expecting an answer from him isn’t such a big deal, I REALLY want him to tell me personally why he’s not providing any more updates.
That crappy maintenance policy should be written down on the page where people pay for ST2 “warning: you won’t get tech support and I’ll ignore you on the forums if you’re going to say you’re not happy about this”.
Since I bought ST2 last year, I’ve only received 1 or 2 beta updates and 2 stable builds. Don’t tell me to use the unstable and backwards incompatible ST3 beta…[/quote]
Let me get this straight. You expect a personalized email from JPS outlining his development plan for sublime. In addition, you want to be able to ignore the fact that st2 was released for a year or 2 before you purchased it and expect that bug fixes only count from the time that you purchased sublime. Wow, just… wow.
The whole point of forums is so that questions can be answered ONCE and then people can search them for answers later. That is why the earlier poster quoted JPS.
Let’s talk turkey for a minute. You’ve received 1 or 2 beta updates and 2 stable builds in a single YEAR of use. Tell me, How many other dev tools update that often? I haven’t seen that many updates to Visual Studio in that time. In fact, once they announced VS2012, I don’t think I ever saw an update to VS 2010. Why is it that you think JPS should do more than an entire team at Microsoft?
You want him to support st2 with updates for more than 2 years and not do any work on new versions?
He works on the new ST and he’s made bug fixes to it already. Would it be such a big deal to offer a new stable version every 2-3 months with some of those bug fixes? It’d take 3-4 hours per month.
Have you tried the dev builds of st2 to see if they fix the issues you’ve had?
Yes, they don’t fix any issue I keep running into.
I’m not a moderator here, so I have absolutely no power, but I have no problem stepping up and saying that I think you’re out of line.
That’s for the best.
I don’t know about you, but I’ve had a bunch of people jumping in and saying it’s unreasonable to expect to receive any kind of update or support and that I should just use ST3. As in don’t expect anything from the developer, just use the latest experimental and unstable stuff.
That worked wonders last year with an even less experimental version of ST.
Please don’t bother to reply. I’m not going to reply again. Thank you.
I thought you said that jps hadn’t responded to you!? Great news that he emailed you to inform you how much effort it would take him to make regression changes to the deprecated ST2 code base.
All sarcasm aside, none of us has any idea what effort jps puts in or how difficult and time consuming any given change would be to make. I agree that his communication skills leave something to be desired, but, as you have admitted, the editor is absolutely amazing. Significant progress is being made on the new ST3 branch and I look forward to the enhancements that will come.
Well, I never said that you can’t expect updates for something you’ve paid for. I have just felt that I did get support on ST2. I have seen bugs that I’ve reported get fixed in the dev builds. It is probably fair to say that some peoples issues have not been resolved. Not to excuse st2, but that’s true of just about any software on the market, and I don’t think that sublime is unique in that regard. I also never felt like the st3 licensing was a money grab. In fact, I think that JPS has done a lot to try to make it affordable to those who have already supported sublime. If it was a money grab, he’d let st2 licensee’s purchase a st3 license now. I fact, I wanted to buy an upgrade license as soon as I saw that st3 was announced, but there’s currently no way to purchase an upgrade license from st2 to st3. As of right now, JPS is actively keeping me from giving him money.
hi,
finally a builtin goto symbol/definition feature… codeintel was a nightmare to me and it finally made me make a step back to netbeans.
is there a way to test/trial ST3? or this a WIP? before spending 70$? 
i loved ST2, if this was working as intended i wouldve already moved over…
Where do I submit ST3 eventual bugs?
super+alt+down doesnt work for me unless i copy the line from the default config and add it to the user config
{ “keys”: “super+alt+down”], “command”: “goto_definition” }
Could it be because there is an additional line with f12 in the default config?
[quote=“whololo”]Where do I submit ST3 eventual bugs?
super+alt+down doesnt work for me unless i copy the line from the default config and add it to the user config
{ “keys”: “super+alt+down”], “command”: “goto_definition” }
Could it be because there is an additional line with f12 in the default config?[/quote]
In the console enter “sublime.log_commands(True)” to see what is actually running. Alternatively, try using the FindKeyConflicts plugin if you do not want to use the console. One of the commands will display all of the commands tied to a particular key.
[quote=“skuroda”]
In the console enter “sublime.log_commands(True)” to see what is actually running. Alternatively, try using the FindKeyConflicts plugin if you do not want to use the console. One of the commands will display all of the commands tied to a particular key.[/quote]
Thanks for helping me out with the sublime.log_commands(True) command, didnt know about it. It was a plugin clash. Removed the plugin which I didnt use anyway.
Thanks!
Agreed. I sympathize with this point, but the problem is that I didn’t pay $60 for programmer output. I paid $60 with a reasonable expectation of an eventually stable product. Therein lies my disappointment.
To finalize ST2 and call it good given its abundance of bugs, quirks, and inconsistencies is a questionable thing to do, IMO. This editor has so much promise with really awesome features, but ST2 in its final form is simply half-baked. I find I am constantly fighting it to do basic things (eg, html code folding is broken; brace matching doesn’t always work; ctrl+d sometimes uses whole-word matching, sometimes not, regardless of whether my initial search was a whole-word search; opening a project opens a redundant ST window in addition to the project; sometimes a paste replaces selected text, sometimes it doesn’t; Word Wrap setting doesn’t stick; many more…). I CAN’T be the only person who’s had this experience. I’m sure these issues will eventually get ironed out and ST will be a properly baked product, but I have low confidence that I won’t have to pay for a few more upgrades until that’s the case.
EDIT: forgot to mention one of my biggest peeves: undoing or redoing an edit does not always jump to the location of the edit so that you can actually SEE what was undone/redone. It’s infuriating.
[quote=“adzenith”]
When I read this, it blew my mind:
Maybe it will blow yours too.[/quote]
I stumbled upon that behavior randomly, and use it all the time now (most often for changing just part of a variable name that appears in multiple places).
[quote=“adzenith”]
When I read this, it blew my mind:
Maybe it will blow yours too.[/quote]
Wow, OK that’s pretty clever. Thanks for this adzenith. My bad for assuming it was a bug.
IMO it could be even smarter, though, by assuming whole-word matching if the current selection is a selected word… just seems to make more sense and additionally avoids the highlighted vs. matched confusion. The editor is just so brilliant in so many ways that perhaps this makes me overly critical when things fall short of perfection.
Running ST3 on OSX 10.8.3, using my (paid) ST2 license.
The sidebar does not refresh to stay synched with the current directory (e.g. when files are deleted or added from a terminal window or as a result of running code). I never had this problem in ST2.
I have experienced this with multiple versions of the ST3 beta. This morning I went through the following procedure:
After the above, I still have the symptom. I can force a refresh of the sidebar via Projects > Refresh Folders, but that’s getting tedious, so wanted to report this as a bug, along with my attempts to resolve thus far. Any suggestions (or fixes 
) welcome!