Dev Build 3086 is out now, fixing some regressions in 3085.

Also in 3086 is support for case insensitive matching in the sregex engine, improving file load speed for some file types.

Thank you! I went from a 4 second load-time on some files to no load-time with the sregex engine. It might not seem like much, but that makes a huge difference in how responsive Sublime feels when you use it for 8 hours.

Looking forward to what’s coming in the future. Keep up the good work!

Agreed!

Thanks Jon

Amazing - feels nice a quick.

One thing I have had the last few builds is a crash when opening the app.

When my theme and colour scheme are enabled, it crashes after about 10 seconds of being opened. Reopening the app disabled both my theme and colour scheme and it runs fine. Re-enabling the theme+color scheme makes it work fine until I do a full quit + restart on the app.

So - it’s probably an issue with Cobalt2 - packagecontrol.io/packages/Theme%20-%20Cobalt2 - I haven’t heard this from anyone else but I’m looking to fix it for myself. Any idea how I can track down what is going wrong?

Also, adding a word to the dictionary crashes the application entirely.

@wesbos: That could indicate a bad interaction with Package Control. Do you manage the two packages locally (i.e. in a git repo) or does Package Control manage them? Try if disabling package control makesit work. If it does, try adding the two packages to the ignore_vcs_packages setting for PC and report results in a new issue at the PC repo.

I tested the load time with a 37mb sql dump.

Build 3084: 1m19s
Build 3085: 1m03s
Build 3086: 10s

I can’t replicate that. Assuming you’re on OSX, you should be presented with a crash report when this happens - it’d be great if you could email it to me.

[quote=“jps”]

I can’t replicate that. Assuming you’re on OSX, you should be presented with a crash report when this happens - it’d be great if you could email it to me.[/quote]

I’m not experiencing it on OSX Yosemite.

Very grateful for the quick fix for the SublimeSyntax push/set conflict. This image shows one of my favorite things that’s now possible, context-conscious brace coloring. The old arbitrary constraint that braces couldn’t really “participate” in coloring despite context or even core semantic meaning (eg object literal vs block vs binding pattern) always bugged me about tmLanguage. Now I can just makes a whole loop one color, conditional blocks another, etc, instead of just the keywords. The colors are just temporary for testing:

This should be available in all languages. I’d love this in PHP and JavaScript for example.

Hi guys! I downloaded latest ST3 dev build and it said that I need to enter license. Is there any topic about this? I just want to test it and submit bug request if I’ll find something. Thanks

From the sublimetext.com/3dev page (that you should have read) where you downloaded ST:

[quote]These are the in-progress versions of Sublime Text 3, and they are updated more frequently. Feel free to use them, but keep in mind you will be running less tested code, and you’ll be seeing many more update notification prompts.
The current Sublime Text 3 dev build is 3086. Details on new dev build releases are posted on the forum
Sublime Text 3 dev builds are currently available to registered users only.[/quote]

So buy a license or wait for the next beta.

It’s possible to mess up the sidebar view using the API. It can lead to data loss when deleting using context menu in the sidebar. Wrong file can get deleted.
It’s an old problem and it is reported here github.com/bizoo/SortTabs/issues/11 but without very specific details.

I think the root problem is that it’s possible to move ‘temporary’ (single clicked from the sidebar - one without an entry created in open files sidebar group) views using the API.

High level repro steps:

1. Install github.com/bizoo/SortTabs/
2. Add some folder to the project with a couple of files, lets say with files ‘1’ and ‘2’
3. Double click file ‘2’ (order matters because we will be sorting by file name)
4. Single-click file ‘1’ (to show the preview)
5. Invoke Ctrl+shift+p -> Sort Tabs Menu -> Sort by file name
6. Close previewed file ‘1’
7. Preview file ‘1’ again (step 4)
8. Again sort by file name (step 5)

Now you will see that sidebar view of open files is broken. The ‘Open files’ header is gone, everything moves up.

JS (ES6) is what I’m doing presently – though I can see how the example screenie doesn’t make that obvious

Bathos - is your work up on github?

I can’t say how excited I am for your ES6 work!

Seems like variables’ lookup always happens in current syntax, even when variable is defined in embedded one.

There are also some weirdness with backreference. This will end with error saying backref number is wrong:

strings:
- match: '("''])'
  push:
  - meta_scope: string.quoted
  - match: '\1'
    pop: true
  - match: (?<!\\)\n
    pop: true

Though if you remove second match it will work.

Really impressed with the parsing speedups in the recent few builds, Jon. Great job, keep it up!

Where can we detect these new scopes to update our themes to take advantage of this?

I just tried ScopeHunter and it doesn’t seem to work anymore.

It works. Try restarting or re-install it.