Dev Build 3119

[maliayas]

There’s a massive refactoring on documentation ( https://www.sublimetext.com/docs/3/ ).

You can see the full diff here:

Update (2016-07-26)

And a plain text diff here:

Commit new files (2016-07-26) as plain text

P.S. I’m not involved in any of the work.

[wbond]

There’s a massive refactoring on documentation

Yes, we did a big cleanup, modernized the style sheet and added the minihtml and scope names docs. There were some additions to the API docs also, and small improvements to other pages.

Due to all of this work, future diffs should be more readable.

[jcberquist]

@wbond: The updated docs look great. They are much more readable. One question: is there a reason the new sublime_plugin.ViewEventListener class is not listed in the API docs yet?

[facelessuser]

There appears to be a bug in minihtml image rendering in 3119. Occasionally, it seems to distort and offset images funny. You can see in the example below the black box had it’s border shaved off the top.

[mrmachine]

Confirming it crashes immediately on launch after updating to 3119. OS X Yosemite 10.10.5 (14F1909).

UPDATE: Tried rolling back to 3118 and 3114, and both still crash immediately on launch. The 3119 update seems to have broken something in a way that also breaks older builds.

Not sure how I can try to recover from this and get back to work?

[OdatNurd]

You may be able to follow the instructions in this forum post to get things up and running again.

[mrmachine]

@OdatNurd Thanks, one of the suggestions over there got me up and running again.

[randy3k]

I am surprised that the typos, e,g, set_async_timeout are still not fixed.

Issue: set_async_timeout should be set_timeout_async

[gigony]

After upgrade, the following command in Console causes a crash in Ubuntu 14.04 LTS
It worked previous versions.
view.show_popup('test', location=1)

I am using “Material-Theme-Darker.sublime-theme” theme.

[kingkeith]

After upgrade, the following command in Console causes a crash in Ubuntu 14.04 LTSIt worked previous versions.view.show_popup(‘test’, location=1)

I am using “Material-Theme-Darker.sublime-theme” theme.

Does it crash with the default theme?

[rppn]

I suggest adding the new APIs to the docs for plug-in developers. I strongly believe plug-ins should follow the way the core Sublime Text behaves, and this would make it easier for us to for example show plug-in settings side-by-side as the new builds. The alternative would be that we poke around in sublime.py, sublime_plugin.py and the Default package every other build.

Maybe it would be possible to ship the docs with Sublime Text for offline use (via minihtml and Help menu), host them on Github to let us add PRs to it and format them for Dash / Zeal as suggested by @alkuzad and @FichteFoll in the Dev Build 3118 thread. A simpler solution would be a single markdown file which can be exported via pandoc to PDF via wkhtmltopdf. I’ve had good experiences with this setup, PDF is fine for most people as you can cross reference and link to external sources.

---

Whatever works best for you. Thanks again for the latest builds, keep up the great work. No issues so far on Win 10 Pro x64 Version 1511 with ST3 Build 3119 x64 portable.

[gigony]

It crashed with the default theme.

So I removed all files/folders in ~/.config/sublime-text-3 folder and installed packages/setting configurations from scratch. Then, it works.

I guess the crash was because install package(.deb) was something wrong or because I am using symbolic links in some folders (such as ~/.config/sublime-text-3/Installed Packages ) which caused sublime confusing?

[wbond]

I suggest adding the new APIs to the docs for plug-in developers.

I agree, if you find any that have been missed, let me know and I can get them added. @jcberquist mentioned ViewEventListener, so I will get that added.

I strongly believe plug-ins should follow the way the core Sublime Text behaves, and this would make it easier for us to for example show plug-in settings side-by-side as the new builds.

I also tend to think that leads to a nice user experience. In terms of showing settings side-by-side, that is accomplished by calling the edit_settings command with the base_file argument. However, plugins will need to handle the situation where that command does not exist (builds before 3116).

The alternative would be that we poke around in sublime.py, sublime_plugin.py and the Default package every other build.

My hope is to continue to improve our documentation, although I don’t know right now exactly what the end result will be. It certainly is a useful experience for package developers to poke around in the Default package since it contains examples of so much. The sublime.py and sublime_plugin.py files shouldn’t be as essential due to the API docs.

[wbond]

I am surprised that the typos, e,g, set_async_timeout are still not fixed.

Thanks for pointing this out!

[frou]

As @mlf said previously, the at-a-glance comprehensibility of what these new inline bubbles are would be improved if they had a little fleck pointing in the direction of the build error they’re talking about.

A plain rectangle appearing in the view does not particularly imply up, down, left, or right to the user. The way it currently looks (even though the position is significant to those in the know) is like a low-spatial-granularity rubber stamp!

[darkred]

When I launched ST 3 build 3118 x64 in win10x64 today
I got "A New version of Sublime Text is available, download now? " in order to update to build 3119.
But, unfortunately, clicking “Download” shows “No update available”.
After that, clicking Help|‘Check for updates’ I get “No update available”.

The above (the prompt to update) reappears every time I launch ST3, but then there’s always “No update available”.

Still today, I get "A New version of Sublime Text is available, download now? " at launch
but then it shows “No update available”.

Just filed this issue:

Issue: Prompt to update on launch which results in 'No Update available'

[FichteFoll]

I agree, if you find any that have been missed, let me know and I can get them added

SublimeTextIssues/Core

Issue: [transfered] List of undocumented API features

[maximsmol]

Should color schemes and syntax definitions avoid constant.character? It is not present in the current list (though constant.character.escape is), but it is kinda stupid not to style char constants.

[ntenney]

For those experiencing crashes on Mac, I found that if I removed this line from my Session.sublime_session that sublime would start up just fine:

“last_version”: 3118,

In my case, it was found near the top of the file.

[rppn]

I also tend to think that leads to a nice user experience. In terms of showing settings side-by-side, that is accomplished by calling the edit_settings command with the base_file argument. However, plugins will need to handle the situation where that command does not exist (builds before 3116).

I’ve found the command already, thanks. I’m more worried about the conditional check against 3116+ for the menu. I’ve so far only come up with nasty workarounds in my head.