Sublime Forum

Sublime Text 3 Beta

#75

BUG3 ?

>>> view.sel()-1] Traceback (most recent call last): File "<string>", line 1, in <module> File "C:\Program Files\Sublime Text 3\sublime.py", line 392, in __getitem__ raise IndexError() IndexError
could be replaced by:

view.sel()[len(view.sel())-1]

but it’s not as elegant as before.

0 Likes

#76

[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]

You are the only one with the numbers but I would suspect the vast majority of your registered users came within the last year and a half. Extended updates for original users is one thing but it seems like you are gouging newer users. $30 upgrade for a $59 piece of software purchased within the last year is hard to swallow. Perhaps you should clarify the upgrade pricing with dates ranges for your users.

0 Likes

#77

BUG:
Selection.add ignore the Region.xpos property, so setting a value for xpos doesn’t work anymore:

class Selection(object): def add(self, x): if isinstance(x, Region): sublime_api.view_selection_add_region(self.view_id, x.a, x.b) else: sublime_api.view_selection_add_point(self.view_id, x)

0 Likes

#78

kramed and the other complainers, your logic is flawed. Here are two options: a) count the beta as a new version. If you think like that, ST2 has been around for over two years so it has a pretty long product cycle. b) Do not count betas as a new version. In that case ST3 is just a beta and you can happily use ST2.

So your argument only makes sense if you do not count the ST2 beta but you count the ST3 beta. That doesn’t make any sense. The developer has done awesome work and ST3 has so many important under the hood chances, which required a lot of work and will significant enhance the user experience. Maybe they are not all visible right away but I am sure more features are going to follow.

0 Likes

#79

@jps

  1. Is it possible to make go to symbol within project pop up previews?
  2. Is go to definition supposed to learn from previous user selections?
  3. Would it be possible to hook into go to definition to filter out irrelevant suggestions?
  4. How do I ignore certain folders in the sidebar from being indexed?
0 Likes

#80

[quote=“kramed”]

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.

You are the only one with the numbers but I would suspect the vast majority of your registered users came within the last year and a half. Extended updates for original users is one thing but it seems like you are gouging newer users. $30 upgrade for a $59 piece of software purchased within the last year is hard to swallow. Perhaps you should clarify the upgrade pricing with dates ranges for your users.[/quote]

IMHO, the main mistake of jps was to not publish a stable build way before…
If it had published a stable build 2.0 back in 2011, and add a few minor build after, no one would complain today.
I bought my license early 2011, 2 years ago, and use ST2 exclusively since, so 30$ now for all the works put in ST look like a bargain for me.

Currently ST3 is in BETA stage with no stable build release date, which could be, if jps follow the same path as ST2, in a very long time.

0 Likes

#81

[quote=“xeno.by”]@jps

  1. Is it possible to make go to symbol within project pop up previews?
  2. Is go to definition supposed to learn from previous user selections?
  3. Would it be possible to hook into go to definition to filter out irrelevant suggestions?
  4. How do I ignore certain folders in the sidebar from being indexed?[/quote]

The GotoDefinition command is defined in a file symbol.py in the Default.sublime-package (which is a zip file) in your installation folder (C:\Program Files\Sublime Text 3\Packages for Windows).
So I suppose you can copy and paste the content of the file in a new file of your User folder, rename the class and adapt it to your need.

0 Likes

#82

Here’s a funny bug, when I open up a directory in Sublime Text 3 on Mac OS I see a whole slew of icons populate my dock that collapse into one. I have a bash alias

alias subl="'/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl'"

and I just open a directory such as subl ~/Library/Preferences/ to reproduce

0 Likes

#83

Any roadmaps for future releases?..
I bought ST2 in May 2012 and from that time got only few updates, last was in September and no official info at all after that! Soon I will pay other $15 (or 30… not sure how much…) and no updates again till 4th will be released? :smile:
All this looks a bit confusing and expensive… even for good text editor.
I’m expecting to have free upgrades at least during next year after purchase and more info about future releases… Please consider this.

0 Likes

#84

Man, I was already behind a number of plugins do to varies reasons. Now I have to port them all…sigh…

Glad to see new builds though. I am excited to see and try out the new stuff coming.

0 Likes

#85

[quote=“bizoo”]The GotoDefinition command is defined in a file symbol.py in the Default.sublime-package (which is a zip file) in your installation folder (C:\Program Files\Sublime Text 3\Packages for Windows).
So I suppose you can copy and paste the content of the file in a new file of your User folder, rename the class and adapt it to your need.[/quote]

Didn’t have time to look into that yet, but would it be possible to show a preview of the currently selected option in the quick panel?

0 Likes

#86

[quote=“xeno.by”]

[quote=“bizoo”]The GotoDefinition command is defined in a file symbol.py in the Default.sublime-package (which is a zip file) in your installation folder (C:\Program Files\Sublime Text 3\Packages for Windows).
So I suppose you can copy and paste the content of the file in a new file of your User folder, rename the class and adapt it to your need.[/quote]

Didn’t have time to look into that yet, but would it be possible to show a preview of the currently selected option in the quick panel?[/quote]

Sorry, don’t understand.
I think it’s already work the way you want:
F12 on a method open a quick_panel with all the occurrence of this name. And when navigating among the results you see a preview of the file in the editor.

0 Likes

#87

All the details behind ST3 have been rather disappointing :confused:

First off, the switch to Python 3 is going to absolutely decimate the plugin community and any backwards compatibility is completely out of the question. Second, not a single bullet point in the list of new features for ST3 seems to warrant a major version increase. Symbol indexing is perhaps the best argument for it, but it’s the only one. Pane management is already available for ST2 (origami). Speed is always a concern and has been improved several times throughout the life cycle of ST2. Lastly there’s the API swapping from Python 2 to 3 which is more detrimental than beneficial.

There is not a single convincing reason to swap to ST3 in the announcement. If anything it is more convincing of the opposite with changes like swapping the API from Python 2 to 3. This all comes off as a rather disingenuous money grab. If you’re going to arbitrarily end the life cycle of an existing product while at the same time increase the cost of it’s replacement, at least present a product that is worthy of that cost. If ST2 licenses were available for $59 side by side ST3 licenses for $70 there’d be no reason what so ever to purchase an ST3 license. ST3 exists for the sole reason of increasing the cost of licenses.

Just compare the announcement of the ST2 public alpha to that of ST3.

Ugh.

0 Likes

#88

Any idea how much the upgrade will cost (for ST2 users)?

0 Likes

#89

@Anomareh, wow, chill out. Upgrading to python 3 is the only way to move forward. The fact that it’s not backwards compatible is old news. Get over it.

umm, how about… no. I don’t really get the point you’re trying to make.

To clear up the money issues that some people (cough Anomareh) don’t seem to understand:
(1.)Your ST2 license works for ST3 while it’s in beta.
(2.)Considering that ST2 was in beta for about a year, I think you’ll be okay. (Not to mention that ST2 was in alpha for a lonnnnng time)
(3.)An extra $15-30 really isn’t asking much.

Also, ST3 is fast as fuck. You should get it.

0 Likes

#90

Anomareh, this is a beta!! The under the hood changes are substantial and will lead to major benefits in the future. I am sure that more features will be added to ST3 before it is finalized. My guess is that the beta introduces the major under the hood changes, which are the foundation for future features that will make us very happy! I don’t see any money grabbing - I rather think that the developer is extremely generous with an unlimited trial period. I haven’t purchased a license myself but will do so this week! Best editor, awesome developer who deserves our support!

0 Likes

#91

Nevertheless I still think the Jon should make a clear statement about the upgrade price - 15$ vs 30$.

0 Likes

#92

jps I think that u could create different repos for the default packages like php, c, etc…
In this way user could fork and improve this package like agibsonsw did.
u can merge this improvement and pull them from repos just before building a new version…in this way u’ll have an always up to date definition, completions, etc for these core packages insted to have us to delete the old and non actual ones XD

just a suggestion XD

0 Likes

#93

I’m pretty sure the only reason you can give me about how swapping to Python 3 is moving forward is that 3 is a higher number than 2. The situation behind Python 2/3 is not a simple one. The fact of the matter is the change to Python 3 is going to decimate the plugin community. Plain and simple. I’ve been using ST since long before ST2 and it took quite some time for the plugin community to get some steam behind it. I work with Python on a daily basis and this change is going to benefit no one. The majority of Python projects are still using Python 2 for a reason: the support for 3 just isn’t there yet. It’s a process that takes time and it can’t be forced.

The main issue behind swapping to Python 3 isn’t even really a matter of Python 2 vs 3. Due to ST3 being a paid upgrade the user base between ST2 and ST3 is going to be split. This puts every single plugin developer beteween a rock and a hard place because of how big of a nightmare it is to make anything but the simplest of code compatible with Python 2 and 3.

[quote=“C0D312”]umm, how about… no. I don’t really get the point you’re trying to make.

To clear up the money issues that some people (cough Anomareh) don’t seem to understand:
(1.)Your ST2 license works for ST3 while it’s in beta.
(2.)Considering that ST2 was in beta for about a year, I think you’ll be okay. (Not to mention that ST2 was in alpha for a lonnnnng time)
(3.)An extra $15-30 really isn’t asking much.

Also, ST3 is fast as fuck. You should get it.[/quote]

Besides symbol indexing none of the new features warrant a major version increase. There have been many updates to ST2 that read like half of the new features. It’s not a matter of the money. It’s a matter of calling ST2.1 ST3 to justify raising the cost of licenses. To everyone saying: “It’s just a beta!” read the original announcement for the ST2 public alpha and compare it to the ST3 announcement.

sublimetext.com/blog/article … blic-alpha
sublimetext.com/blog/article … ext-3-beta

Not to mention 99% of the time the word beta isn’t even used in a proper manner. Now-a-days it’s a just word people slap on to whatever they’re selling to justify selling a product before it’s finished and to have an excuse at the ready for any bugs that arise. “Oh it burned down your house you say? Well it’s in beta!” He is selling ST3. You can’t buy ST2. He can call it whatever he wants, it doesn’t change the fact of the matter.

Also the latest stable release of ST2 blows the ST2 public alpha out of the water speed wise. Your point?

0 Likes

#94

Great progress JPS. Thanks for the v3 updates. Looking forward to what else is in store.

0 Likes