Sublime Forum

Dev Build 3127

#22

Just got the build! I haven’t experienced any problems so far, but I have a small install with barely any plugins. I love all of the new tweaks like the Theme selector under “Preferences” menu, and I also really dig the new Default and Adaptive themes, I’m switching to those.

None of my plugins (including SublimeLinter and Vintageous) are broken. This build is great, thanks Sublime HQ!

0 Likes

#23

Seems like disabling BracketHighlighter prevents Windows from breaking (so far). OSX is still working fine with BracketHighlighter.

2 Likes

#24

Indeed, this looks to be the problem.

Let’s contact the plugin author! Oh, wait… :smiley:

0 Likes

#25

Here on my Linux machine (haven’t tested other platforms yet), in a newly created window the command palette does not render properly the first time it’s displayed, as shown in the image. Closing and reopening the palette again clears the issue.

This is the native size that windows are created for me, which is fairly small and so may or may not play into what’s happening.

0 Likes

#26

Ikr

Sigh…now I have to figure out why…and why just Windows :confused:.

0 Likes

#27

Is this the Adaptive theme, or something you customized? Knowing will just help in reproducing the issue.

0 Likes

#28

Why not support for font ligatures like fira code & etc…

1 Like

#29

That’s the stock Adaptive theme (and Monokai as the color scheme, but I doubt that matters). It doesn’t seem to happen for the Default theme.

Additionally, now that I’ve swapped to the Default to check and back to the Adaptive one, it also doesn’t happen any longer, including after a restart.

Possibly there was something wedged in the session information or something?

0 Likes

#30

Any idea if this has a quick fix?

0 Likes

#31

Because, from my understanding, it will require a significant amount of reworking how we handle font glyph caching and layout. Jon is the expert in this area. Previously he mentioned that he would like to do it, but it won’t be “soon”.

0 Likes

Support for font ligatures
#32

As of build 3127, all API calls now return and accept device-independent pixels. Previously on Windows and Linux some returned/accepted device pixels. My guess is that it is related to that.

0 Likes

#33

"line_height_workaround": false,

Looks like line height issue got fixed :confetti_ball:!

0 Likes

#34

Hmm, it looks like autocompletion results have shrunk for some reason. Does it have to do with the new DPI features? On Windows 10.

0 Likes

#35

Created issue for BracketHighlighter:

Short term, disable BH or defer upgrade until I can track down why I’m destroying ST 3127 on Windows. I’m not looking into this tonight though. It’s late and I’ve got stuff to do :slightly_smiling:.

3 Likes

#36

Yep, that did it. Thanks :slightly_smiling:

0 Likes

#37

Okay, I lied. I spent just enough time to identify what exactly is breaking ST (don’t have a fix yet). Gutter icons in BH are breaking ST. When I disable gutter icons by setting them to an empty string, BH no longer breaks Windows. I am curious if other gutter plugins are breaking Windows as well.

0 Likes

#38

Thanks for the report!

0 Likes

#40

will this feature supported in future

0 Likes

#41

I’m also using sublime linter, and that works good.

0 Likes

#42

I’m not sure of all the specifics that cause the issue, but when I set the gutter parameter in add_region to an empty string instead of the gutter icon, BH no longer brings down ST. It’s possible there are more variables that need to be aligned just so before the gutter can cause the issue, but removing the gutter icons fixes the issue with BH for me. Before, ST would be brought down as soon as BH performed a match, but now it seems to have no issues.

Keep in mind, I spent only enough time to identify how to keep from failing, I haven’t explored whether there is a combination of settings that need align to cause this.

0 Likes