Dev Build 3119

[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.

[darkred]

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

Just filed this issue:

I solved this by clearing history in IE: (see here for more details).
pressed Tools | Internet Options (General tab) | Delete,
in order to delete temporary files(using the default settings).
After that, the update completed successfully.

[wbond]

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.

Could you give an example of how it is commonly used? I may have just missed it in my digging and rewriting. All of that documentation is more or less a brain dump of having rewritten a whole bunch of the syntaxes and having looked at some of the statistics dumps done in A convention for scope naming.

[wbond]

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.

Is there a way I can reproduce this output? Also, what platform are you on? Are you using HiDPI/Retina?

[facelessuser]

Is there a way I can reproduce this output? Also, what platform are you on? Are you using HiDPI/Retina?

There seems to be a number of factors. It can occur in popups and in phantoms. See issue here:

Issue: On very first draw, topmost phantom is cut off

In the case of the issue above, I couldn’t reproduce it, maybe it was a combination of font size, line height, and/or image size.

In the picture I posted earlier, this occurred in a popup, I increased the image size and I saw some image distortion, and when I increased the size a little more, I saw the second image in the popup get cropped. This was not an issue in
3118.

I replicated the popup issue on my Mac low dpi. The phantom issue covered in the github issue was on a Windows machine, but I do not know the resolution of his screen.

---

Lastly, I have noticed yet another issue in 3119. I have a couple of color schemes that define popupCss, but in 3119, it appears it doesn’t always recognize them. Sometimes it does, and sometimes it doesn’t, but it leans heavily towards not recognizing them. If I remove the popupCss, then of course it uses the internal generated style. It seems to only really want to use the generated one, and if you define your own, it gives you a white popup with black text. It is fine if I feed my own CSS in through show_popup or add_phantom.

[wbond]

I have a couple of color schemes that define popupCss, but in 3119, it appears it doesn’t always recognize them. Sometimes it does, and sometimes it doesn’t, but it leans heavily towards not recognizing them.

If you could link to one’s you’ve seen it on, that would be helpful in me trying to debug. We generate some CSS that is always prepended to the stylesheet, for setting things like the background-color, font and font-size. With 3119 we now also prepend color variables to popupCss and phantomCss. There may be a bug somewhere in there.

[facelessuser]

@wbond Here’s one: https://github.com/facelessuser/Aprosopo/blob/master/Tomorrow-Night-Eighties-Stormy.tmTheme.

[wbond]

I replicated the popup issue on my Mac low dpi. The phantom issue covered in the github issue was on a Windows machine, but I do not know the resolution of his screen.

I just tried to replicate, but was unable to. Perhaps create an issue at https://github.com/SublimeTextIssues/Core/issues with your setup and what plugin, settings, etc? If you’ve already done that, just point me in that direction.

[facelessuser]

@wbond, I figured out the issue, 3119 is not stripping out \r from popupCss. If I switch to unix line endings in the scheme, the problem goes away.

[facelessuser]

@wbond as requested:

Issue: popupCSS in a color scheme saved with Windows line endings causes white popups

This was tested in portable ST3 3119 with no plugins installed.

[facelessuser]

I will have to see if I can create a scenario to replicate this image distortion issue better. Once I have that, I will create the issue.

[wbond]

This was tested in portable ST3 3119 with no plugins installed.

Perfect. I copy-pasted the color scheme to a file on my machine, and I default to unix line endings. Thanks for figuring it out!

[jps]

With regards to image distortion, we’re not currently snapping anything to pixel coordinates within minihtml, so if margin, padding or line height introduce fractional values, then the image can be drawn at a non-pixel aligned location, which may account for some artefacts, but the cropped border above doesn’t really look like this