I will more than likely release the new BracketHighlighter2 for ST3 and also update HexViewer for ST3 as my priorities.
I have a number of other random plugins that will eventually get updated as I have time.
When all of this will startā¦I donāt know. I have had a number of things that have been keeping me from my development recently that I am hoping will die down soon.
Cmd+Shift+R doesnāt display previews, but it looks like it can be taught to do so, analogously to F12. Hereās a relevant excerpt from the implementation of F12:
As far as I know cmd+shift+R doesnāt show previews because you can have multiple definitions of a symbol. If you press enter on a symbol, it gives you a list of their definitions and has previews there.
You really like to contradict yourself, donātcha?
First you argue that Python 3 is too big a change since it will warrant people rewriting plugins (which will take some time but may prominent plugin authors have already given their support and mentioned that they are working on porting over to Python 3). Then you argue that there is not enough changes (in terms of features) but I would argue that the switch to Python 3 is pretty major.[/quote]
What? Talk about taking something completely out of context just to make an argument. Never did I say there were not enough changes in Python 3 to consider upgrading. I said that the differences between Python 2 and 3 arenāt the main reasons the upgrade is a problem.
Swapping to Python 3 is not moving forward. Itās running across the canyon before the bridge is built.
Except everyone is as ST2 is EOL and canāt even be bought anymore (and no, having the ability to buy ST3 and get a copy of ST2 for free is not having the ability to buy ST2)? ST1 didnāt see a single update (bug fix or otherwise) once the ST2 public alpha became available. I donāt see the situation between ST2 and ST3 being any different. Looking beyond how insane it is to compare a programming language to a text editor, Python 2 is still being maintained and itās still available.
So you can see into the future? What reasons do plugin developers have to update their plugins for ST3? With a split userbase theyāll just be choosing one userbase over another. Largely because, as I stated, there arenāt enough improvements in ST3 to justify upgrading. Also, I like how you believe ST3 is going to see a bunch of new features added at some point. The majority of the new features of ST2 were available in the public alpha. Only a couple were added afterwards. I donāt see any reason for ST3 to be any different.
Besides you completely missing the point I was making, you do realize ST3 is the only thing available for purchase right now right?
Again, you somehow completely managed to miss the point I was making. Speed isnāt a viable reason in the case of ST to increase the major version. As he stated himself, speed has always been a concern and has always seen improvements. ST being faster is not something new to ST. STās speed has been substantially improved several times throughout the development of ST2.
@Anomareh well, this conversation was fun at first but now I see youāre not even going to read what Iām saying so thereās no pointā¦(plus Iād prefer if we stopped mucking up this thread for people with legitimate stuff to post)
I gotta go to bed anyway. Iāve got computer science class in the morning and weāre learning about methods! yay!
Funny. First off, you started the discussion by responding to my thoughts on the ST3 beta. Second, you took nearly every single thing I said out of context. Third, I even obliged and directly responded to everything youāve said. Also, I donāt see how this is off-topic in a thread designated for discussion about the ST3 beta.
Port some plugins before making a final judgement.
I started porting efforts by writing a plugin that opened errors in ST2 where I did all my editing.
I ported an old lxml plugin that parses html buffers in a background thread, making use of the now threadsafe scoping api.
Itās constantly building a DOM as you type, without ever slowing down. You couldnāt really do that in ST2.
Thereās subtle changes like all plugin modules having absolute path __file__ properties so you can write exception handlers that navigate to source of errors and navigate the backtrace.
The speed improvements are very much a consequence of changes to the plugin system and plugin loading, breaking changes that couldnāt really be backported to ST2.
Having said all that, Iām somewhat disappointed thereās not more radical changes too, with all this breakage/porting pushing ETA on ST4 well into the future.
Subtle isnāt really the word you want to see describing a new major release when a price increase comes attached to it
āHereās this thing that for the majority of end-users is the same as the last thing except this thing is more expensive and itās going to break nearly everything for a while. Oh, and itās faster. Also, you canāt buy that last thing anymore and itās no longer supported.ā
[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]
[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).[/quote]
Future major versions, such as Sublime Text 4, will be a paid upgrade.
The download link still points to ST2 for me?[/quote]
You can still download it, but you canāt buy it. You can buy ST3 and get a free copy of ST2, but you canāt buy ST2. Also, I highly doubt ST2 will see another update from here on out. For all intents and purposes ST3 has been released and is the only product that will see development.
You can still download it, but you can't buy it. You can buy ST3 and get a free copy of ST2, but you can't buy ST2. Also, I highly doubt ST2 will see another update from here on out. For all intents and purposes ST3 has been released and is the only product that will see development.
You canāt actually buy older version of software in general (except software that is sold on phisical support). Why would ST be an exception?
Do you, for example, want Jon to backtrack, porting everything possible back to ST2 in a non breaking manner?
Do you want a promise of at least bug fixes for ST2?
Itās not as much progress as you or Iād like, but ST3 IS progress. Iād rather see a mass transition ASAP.
What Iād like to see is a promise of bug fixes for ST2 for a reasonable period and wbond officially compensated for work in speedily porting Package Control and managing the transition.