Sublime Text 3 Beta

[wbond]

Package Control has been initially ported to ST3. Right now it is broken on Windows due to a lack of the ssl module. Definitely works on Linux and should work on OS X with build 3008.

wbond.net/sublime_packages/packa … lation#ST3

Right now it is just a 1-to-1 port to Python 3. None of the changes necessary have been made yet to support specifying what version of ST a package works with, or support for not extracting .sublime-package files. The install only works from Git due to the CA certs needing to be able to be loaded from the filesystem for the various downloaders. Probably later tonight I will find a way to get it to extract the certs so the console install will work again.

[kemayo]

Quick panel seems to have picked up a small bug, if you have a slightly inconsistent list.

If you do:

results = 'one', 'two', 'three']
self.quick_panel(results, self.panel_done,
            sublime.MONOSPACE_FONT)

It works fine. But if you do:

results = "part one", "subtext"], 'two', 'three']
self.quick_panel(results, self.panel_done,
            sublime.MONOSPACE_FONT)

…the entries without the subtext get cut off.

This is fixable by just making sure all the list items are in the subtext form, but it’s still a regression from ST2.

[qgates]

@kemayo. Confirmed regression with quickpanels

[fgimian]

Hello everyone,

I purchased in August last year. For what it’s worth, I must agree with several people in regards to the extremely fast paid upgrade to v3, I think it is a bit unfair to customers who purchased the product in the last few months, especially since there are no compelling new features (yet). My suggestion would be $15 upgrades to those who purchased in the last 6 or so months, although I will definitely purchase the upgrade even at $30 to support the development of this amazing editor (I can’t begin to explain how much I love it!!!).

Now onto more important things…

A few feature requests which I really really hope you’ll consider:

Notepad Replacement

Sublime Text 2/3 does not support the -z option correctly for replacing Notepad on Windows machines. See Windows Notepad Replacement. I have been using the small exe here (github.com/grumpydev/Sublime-No … eplacement) to do it which has worked OK so far, but this really REALLY should be built right in. Especially now that ST3 opens as fast as Notepad, there’s no reason at all that all Windows users wouldn’t replace Notepad with it. I used to use this all the time with Notepad2 (before discovering ST2).

Legacy Themes (on Windows)

In Windows, ST2/ST3 still use legacy themes, making the application look like it’s running on Windows 98

vs

Can you please use theme support for your dialogs on the ST3 Windows build?

Font Reset Issue

Preferences / Font / Reset does not seem to respect the following attribute I have defined in my user settings file:

“font_size”: 13

It also doesn’t seem to follow what’s in the default settings file (if I override it). Instead it always seems to reset the font size back to 10. Can you please repair this to follow the font size set in settings?

Syntax Highlighting for Markdown with Monokai

I don’t see syntax highlighting working with Markdown and the default Monokai theme (which is my favourite). Why is this the case?

Cheers

[FichteFoll]

[quote=“fgimian”]Font Reset Issue

Preferences / Font / Reset does not seem to respect the following attribute I have defined in my user settings file:

“font_size”: 13

It also doesn’t seem to follow what’s in the default settings file (if I override it). Instead it always seems to reset the font size back to 10. Can you please repair this to follow the font size set in settings?[/quote]

Due to how the font size adjustment works this is not possible because it edits the settings object and saves the changes into “User/Preferences.sublime-settings”. Resetting the font size erases the entry in the file completely and results in ST using the default value. For reference, see “Default/font.py”. However, try this plugin: github.com/SublimeText/RevertFontSize/

[Saxi]

Looks like JPS stepped out of this thread when too many people started complaining about upgrade pricing but hope you get to see this.
I bought Sublime Text 2 at the end of November, and would agree it should fall into the “upgrade” window, but I would pay for the upgrade regardless as it is something I use and love daily.

But I don’t see me upgrading to ST3 for one big reason, plugins. I am all for efficiency and speed, in fact I’m a junkie regarding this. But it is going to be some time 6-12 months before the plugins I use and depend on have support for ST3. I don’t want to have to learn python and hack them myself, and some of them are likely not maintained much making it very slow for them to get updated. For me, a lot of my workflow depends on certain plugins. Some of them I really depend on.

[wbond]

But I don’t see me upgrading to ST3 for one big reason, plugins. I am all for efficiency and speed, in fact I’m a junkie regarding this. But it is going to be some time 6-12 months before the plugins I use and depend on have support for ST3. I don’t want to have to learn python and hack them myself, and some of them are likely not maintained much making it very slow for them to get updated. For me, a lot of my workflow depends on certain plugins. Some of them I really depend on.

I have a feeling that many of the big popular ones will be ported in a few weeks to a month (I am working on mine right now). The simpler ones are probably easier to fix. The 2to3 binary that comes with Python 3 helps quite a bit if you don’t know all of the changes between 2.6 and 3.3.

[sublimator]

I have a feeling that many of the big popular ones will be ported in a few weeks to a month

That seems like an accurate assessment to me

[Saxi]

[quote=“wbond”]

But I don’t see me upgrading to ST3 for one big reason, plugins. I am all for efficiency and speed, in fact I’m a junkie regarding this. But it is going to be some time 6-12 months before the plugins I use and depend on have support for ST3. I don’t want to have to learn python and hack them myself, and some of them are likely not maintained much making it very slow for them to get updated. For me, a lot of my workflow depends on certain plugins. Some of them I really depend on.

I have a feeling that many of the big popular ones will be ported in a few weeks to a month (I am working on mine right now). The simpler ones are probably easier to fix. The 2to3 binary that comes with Python 3 helps quite a bit if you don’t know all of the changes between 2.6 and 3.3.[/quote]

Agreed, but it just takes one or two critical ones to disrupt the workflow and make upgrading not worth it.
One plugin I use a lot and would hate to lose is Corona Sublime, but I suspect it would take some time for that to be updated.

[sublimator]

github.com/drowne/Corona-Sublime

This doesn’t actually seem to have any python plugins?

Packages that are just syntaxes/snippets etc should just work

[sublimator]

I have a feeling that many of the big popular ones will be ported in a few weeks to a month

Emmet (ZenCoding) unfortunately relies on PyV8, which last I checked a month or so ago, isn’t Python 3 ready yet.

Porting that to Python 3 will be a bit of a task

[nollo]

Jon, can we expect to hide menu under Linux ? I really miss this feature !

Thanks for your work

[FichteFoll]

[quote=“bizoo”]For ST3 (Windows) after a quick look at the portable version:
(- show_quick_panel has a new on_highlight callback ! Yeah !!! thanks Jon.) [this is not a feature request but whatever ]
- Still no way to know what’s modified on the on_modified event… [Not too necessary but could reduce ressources needed in order to see what has changed]
- Still no way to add custom information in the status bar (like indentation and syntax) ? [That’d be insanely awesome, for instance with line endings]
[/quote]

I’d really like these features in ST, please add them to your roadmap if they aren’t already.

[quote=“jps”]Indexed symbols are controlled by the showInIndexedSymbolList preference, which is defined in .tmPreferences files. Most syntax definitions are covered by the contents of Default/Symbols.tmPreferences, but the scala syntax definition appears to assign scope names differently.

In short, you need to edit “Packages/Scala/Symbols.tmPreferences” and change it to: …][/quote]

The default implementations use a file named “Symbol List.tmPreferences” for this but after testing various file names it seems like this doesn’t matter at all. It even doesn’t matter if the “name” key inside is not “Symbol List” so it appears that the only interesting parts about them are that it the file contains dict which has a “settings” and a “scope” key. Anyway, regarding the tmPreferences and other tm* files, I created a new topic about xml not being the best choice because this is a new issue and does not revolve here. ST3 might be a good opportunity to take this step now or at least soon.

Deprecating tm* settings files (and maybe using YAML)

Editing tm* files (tmPreferences, tmLanguage, tmTheme) just sucks. This post is to convince the developer(s?) to deprecate the tm* files and possibly implement a new language settings system. I tried to structure it somehow well but considering I wrote this over 3 days it might still be a bit complex. Don’t hesitate to ask if you can’t follow or don’t understand something. Probably the only reason why tm* files are used seems to be backwards compatibility with TextMate. However, the reasons aga…

[laughedelic]

I just want to support all those people who complain about price increasing. Don’t like new price policy at all. Especially taking in account that features like speed optimizations should be just a part of normal application development (not an indicator of a new release), and pane management was pretty the same in ST2 with origami plugin.

It all looks like the late Apple updates — you should call this new release Sublime Text 2S. If it’s just about money making, I start to regret that I switched from Vim and spend my time on configuring Sublime and writing plugins…

[heardtheword]

I came across an issue with show_quick_panel in ST3 when I want to show multiple panels in succession. The first panel shows fine but apparently doesn’t release until after the selection method is called. I found a workaround using threading.Timer but it is much more convoluted than simply calling show_quick_panel in the select callback. I’m on a Mac if that makes any difference.

[drcongo]

I too would like to complain about the upgrade pricing, it’s far too cheap. I make a decent living coding in Sublime Text all day and using two of my brain cells was able to formulate a basic understanding of its value to me. While doing this, two of my other brain cells were busy coming to the conclusion that if Jon had simply spent the next six months twiddling his thumbs, sipping fine wine and lounging on his huge pile of well deserved cash instead of working his butt off, then there wouldn’t be an endless stream of ingrates criticising him for daring to charge for his work.

Now, where’s the donate button so I can show some extra appreciation for all the man-hours ST has saved me?

[FichteFoll]

I came across an issue with show_quick_panel in ST3 when I want to show multiple panels in succession. The first panel shows fine but apparently doesn’t release until after the selection method is called. I found a workaround using threading.Timer but it is much more convoluted than simply calling show_quick_panel in the select callback. I’m on a Mac if that makes any difference.

Confirmed.

window.show_quick_panel("some", "items", "in", "this", "list"], lambda x: window.show_quick_panel("duh"], print), on_highlight=print)

[2to3]

Bought ST2 in December 2012, and 1 month later discovers it’s EOL, and that even if I qualify for the cheaper upgrade (which I am not sure if I am), I would still have been better off buying today instead.

This is really disappointing having to pay 25%-50% more after one+ month of buying it, especially with no indication of it going EOL (it’s version 2.0.1!)

[Shubit]

First of all I must say that Sublime Text is the best text editor in the world and all the changes coming with Sublime Text 3 will make it even better.

About the pricing:
I’m just a student and Sublime is just a text editor, with many alternatives out there for free. And while you don’t have much money as a student, you get many things that you might need for studying for free (Microsoft products) or least a discount, except Sublime Text. If I would be already working and Sublime Text would help me to earn money, the old 59$ and the new 70$ would be fair price. But I don’t and therefor buying Sublime Text 2 last autumn was a big investment for me. Since then Sublime Text 2 hasn’t seen any updates and now I can switch to Sublime Text 3 Beta, but it will take some time for the plugin developers to update and when they are done it will not last long until Sublime Text 3 is released and I would have to pay another 30$ or go back to Sublime Text 2.

About the changes:
I think the step to Python 3 is right, some might argue that it is too early, but Python 3 is the future and someone has to go forward first (before the other follow).
The promised speed improvement would be very cool, but so far I can only test ST3 without plugins and without plugins ST2 starts instantly as well for me. So I have to wait for some plugins ports so see if ST3 slows with them as ST2 does. Also speed was always a trademark of Sublime Text, so any speed improvement I see more as a bug fix than as a new feature. Therefor I would have expected those improvements as small updates to Sublime Text 2 over the last months. While there were no updates I paid the 59$ for the program without getting any bug fixes (and the lack of speed was not the only bug).
The improvements to the Goto feature are very nice, but do not satisfy a major update for 30$.

Conclusion:
I’m happy to see the movement forward and I appreciate Jon’s work, but I’m very disappointed from the update policy. First no updates for Sublime Text 2 and now the expensive update. 5-10$ would be ok for me (as student) if Jon adds some more little features.
Further I think a cheap update would guaranty that most of the users switch as soon as the plugins are working. Then the plugins developers can focus on the new version and the user base would not split (which would be very bad).

[icylace]

Sublime Text 2 has had a huge impact on my productivity and added a lot of fun to the work I do. I’ve been testing out ST3 and like it a lot. I personally would be willing to pay a lot more for the upgrade. I’m no longer a student but I think discounts for students should be considered.