First off, so far ST3 looks very cool, that instant startup is is very nice. Price is more than fair, imho, for what you get.
Tiniest of suggestions: could you maybe change the program icon to something else? Since I run v3 in parallel to v2 (for the plugins), it’d be nice to differentiate them in the toolbar… (I for one love this icon: dribbble.com/shots/442575-Anothe … st=buckets )
Cheers
One thing I notice in ST3 that’s a bit annoying is that if you click on the code map outside the current area (the grey tinted area), you can’t immediately drag that area. This was possible in ST2 and was super convenient - you’d click anywhere on the code map, the active (grey) area would jump there and you could drag it around. I hope that’s just a bug in ST3?
@ripclaw: This was implemented in ST2 Dev 2220 and can be disabled: sublimetext.com/dev
…ripclaw is right, ST3 has a regression here. While “minimap_scroll_to_clicked_text” exists, in ST2 you could click on the minimap column to jump to a location, and then drag to immediately start scrolling without letting up on the mouse. In ST3 you have to click once to jump to a given view, and then click again to scroll.
“minimap_scroll_to_clicked_text” also isn’t in the default Preferences.sublime-settings, and probably should be?
Hi.
Could we expect that these requests will be addressed:
sublimetext.userecho.com/topic/5 … n-support/
?
It’s the main thing that keep me away from SublimeText for a while (and using emacs)
Thanks.
I’m still using the trial version of Sublime and was just about to make the purchase before this all kicked off.
Sublime is a very nice piece of software, I’m very impressed with it. Along with SublimeClang, Astyle and a couple of other plugins I finally have a Linux workflow that works well for me.
I would agree with the comments regarding upgrade pricing though, $70 is a fair price to pay for such a well engineered editor. But, as is normal in the software industry, a period of upgrades should be included in this price.
As it stands I’m forced to evaluate whether this particular build “SublimeText 2.0.1 build 2217” will meet my needs exactly as is, bugs and all - my $70 does not subscribe me to a living project that has the potential to improve and evolve.
That’s a shame.
[quote=“marcuso”]As it stands I’m forced to evaluate whether this particular build “SublimeText 2.0.1 build 2217” will meet my needs exactly as is, bugs and all - my $70 does not subscribe me to a living project that has the potential to improve and evolve.
That’s a shame.[/quote]
All licenses purchased from the ST3 beta announcement onward are valid for ST3 and ST2, as I understand it. See sublimetext.com/sales_faq for confirmation of this.
Ok, that’s a bit better - I’ll be able to get 3.0 when it’s eventually released
So, people who’ve purchased “recently” are only $4 worse off than me ($15 upgrade price minus $11 price increase that they didn’t have to pay)
I think I’ll get my wallet out, purchase and then gleefully cackle at what I’m going to spend that $4 on ))
Tried ST3 tarball on Ubuntu but Go To Definition menu inactive (PHP project), is that a bug or not implemented yet for Linux/Ubuntu?
Thanks for you work
I little question.
I bought yesterday a license for this awesome software.
When 3.0 will come out my license’ll be valid for that one too??
Thanks and keep up with your splendid code!
[quote=“cisco88”]I little question.
I bought yesterday a license for this awesome software.
When 3.0 will come out my license’ll be valid for that one too??
Thanks and keep up with your splendid code![/quote]
Yes. Quoting sublimetext.com/sales_faq:
[quote]Upgrade Policy
A license is valid for Sublime Text 3, and includes all point updates, as well as access to prior versions (e.g., Sublime Text 2). Future major versions, such as Sublime Text 4, will be a paid upgrade.[/quote]
I think it’s pretty clear that ST3 is an artificial major version cutover (on an otherwise continuous development timeline) designed to generate more revenue. You’d have to be pretty naive not to see it.
That said, I don’t begrudge someone asking for compensation for the fruit of their labor. Developing software is a much more expensive effort than most realize. Furthermore, Jon is under no moral obligation to accommodate anyone else’s ideas about what they feel entitled to; he can set the price of his product wherever he likes. If you don’t think it’s worth it, buy a competing product instead. It’s a free market. No need to get emotional.
That said, I do want to throw my own 2c in: I now have a very different picture of what I thought I was buying into when I spent $60 on ST2. I now know that at this pace, ST won’t fully reach its promise of a full-featured, reasonably bug free code editor for another 3 or 4 versions at least, and I personally don’t think that’s worth $180 or more all told. Too many of the features in the final version of ST2 - albeit AWESOME features in part - are simply half-baked, and the feature set is far from comprehensive. I’ll check back in after a few years and let the early adopters fund the development in the meantime.
if everyone was thinking like you, there wouldn’t have Sublime Text at all. I know, st is not perfect, but for a one man program, it’s fucking awesome! It make me more productive on every work day than any other editor i’ve tried!
my own 2c
Agreed.
Agreed. But for a $60 program, it’s not quite as fucking awesome as I hoped it would be.
It’s a move to Python 3 for one, which is kind of a large improvements. The plugin system is much nicer now and ST2 plugins don’t work anymore.
There is a small bug I met:
Closing current project via command console is not the same as closing project with menu item. Actually when I close project with menu item “Project -> Close project” it works well. But in case when “Ctrl+Shift+p -> project close” project is not closing. Just all dirs become removed, but project stays active.
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.