There’s improved unicode support, a bunch of fixes, and the latest Packages changes from the GitHub repo are in there too.
This build was originally released earlier today as 3096, but introduced a couple of regressions which were fixed in 3097. 3098 further fixes an update check issue on OSX. If you are currently running 3096 or 3097 on OSX you’ll need to update to 3098 manually by downloading it again.
On the subject of dealing with sidebar, could you give us some attributes on sidebar when it gets focus, so that we can render it in a different way so that the focused sidebar could be easily distinguished from unfocused sidebar. I’ve talked about it here in the forum
I’m very glad to see this and to see the project is still active. I just wish there was a way to communicate with the dev ( @jps ). For example if you report a bug/ask a feature you have no idea if anyone actually read your request. Was it approved? Was it rejected? Will it ever be considered? It would be really nice and go a long way if there would be some kind of communication.
In my (hopeless?) case i’m still hoping for a Python update (specially the SSL so it can support TLS1.2 as looks like everybody kind of disables anything lower than TLS 1.2 and you can’t make HTTPS requests anymore form your plugin.)
TLS 1.2 is available via PyOpenSSL or oscrypto. It is not part of Python 3.3’s ssl module, and would require upgrading to Python 3.4, which would break many packages, so it is not a simple choice.
oscrypto gets you “free” patching of the TLS library, whereas PyOpenSSL requires new builds with each release of the cryptography package. I wrote oscrypto, but also wrote scripts to package PyOpenSSL for Sublime Text: https://github.com/codexns.
I’m looking into seeing if/how I can use oscrypto for my plugin, and thank you for it. But this is kind of an workaround due to the fact that sublime does not support it natively isn’t it?
I agree that Upgrading Python might break some packages, but it’s not like we switch from 2.x to 3.x. The problems should not be that big, and we kind of need to do it at some point, I don’t think remaining outdated forever is a great option.
This is a bit odd. Opening files from traversing the output result does actually open the files for me on Windows and orward slashes are usually not an issue, but it does not open files from .sublime-package archives, such as the currently failing Packages/Java/syntax_test_java.java. To my knowledge, the only way to open these files in a simple manner is
These issues were both fixed in the latest build (now 3099). They were both specifically with the code in run_syntax_tests.py in the Default package. The first issue had to do with “” in a relative package path when using that path with sublime.load_resource(). This was occurring where the active view was a syntax_test file when attempting to run the tests in that file. The second issue was also fixed, and the issue was that the regex listed ('^.SYNTAX TEST "?(.?)"?$'), when applied to a first line such as <!--- SYNTAX TEST "cfml.sublime-syntax" ---> results in a group one match of cfml.sublime-syntax" ---> because the quote is optional and it is attempting to match to the end of the line.