Dev Build 3119

[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

[jcberquist]

I should note that while this was happening for me on my main ST install, on a 3118 portable build that I let update to 3119 (and it didn’t happen on 3118), and on a portable 3119 version, after I had rebooted my computer the next day, it was gone. It hasn’t recurred since.

[ntenney]

I know this is the wrong version, but the mac crash still happens on 3120.

[jps]

Thanks for the report

[rppn]

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

@wbond On a similar note, the same thing happens when using plist files like I’m doing it here:

Issue: Ability to apply different indent styles to completions and snippets

If you have *.tmPreferences files with windows line endings in that setup, it completely messes things up.

As @FichteFoll says there:

If there was better tmPreferences integration for variables such as these, things like SublimeText/AsciiDoc@c8ea594 could also become feasable.

Especially the support for piped lists would be nice.

[asmodai]

On Ubuntu 16.04, when using the Goto Anything functionality, the popup window’s entry textbox shows a black background coloured dot when you enter a space. As soon as you enter other text it is changed to the more typical transparent space. Same applies for tab, but then with a dash instead of a center dot.

Not sure if this was an intended change.

[asmodai]

Also, saw someone mention 3120; on Ubuntu 16.04 I have with 3119 installed, no popup for downloading the new version.

[kingkeith]

On Ubuntu 16.04, when using the Goto Anything functionality, the popup window’s entry textbox shows a black background coloured dot when you enter a space. As soon as you enter other text it is changed to the more typical transparent space. Same applies for tab, but then with a dash instead of a center dot.

Not sure if this was an intended change.

Basically it seems to honor the "draw_white_space" preference. Also confirmed on Windows. Affects all quick panels. Not sure if/when behavior changed. IMO I like it the way it is now

[asmodai]

I’m using the default, which is set to selection, so that would make it weird for mine to show this behaviour at least.

[maximsmol]

I am talking about scoping character literals. In languages like C or Haskell expressions like 'a', 'b', '\0' are not strings, but rather a standalone syntaxic construct. In the doc it is not clearly described how to scope these.

By looking at an old syntax file (Pacakges/Haskell/Haskell.sublime-syntax) I see that string.quoted.single was used for character constants.

Should we stick with that? It seems to me that although the information is not lost (color schemes could target string.quoted.single.c and match only character literals), scoping a character literal as a ‘string’ is kinda wrong. Also, in my opinion, targeting language-specific scopes is wrong and is against the point of having a scope-naming standard.

[kingkeith]

Syntax and color scheme authors will probably also be interested in the new Scope Naming documentation.

@wbond: currently the minimal scope coverage recommendations don’t include markup., is that intended?

[wbond]

@wbond: currently the minimal scope coverage recommendations don’t include markup., is that intended?

Not really, mostly that is the case that I’ve done minimal work with syntaxes that use markup.. I’ll put it on the list to get some recommendations in there.

[FichteFoll]

I’d be interested in the markup.raw scope for inline highlighting (with background color) besides the obvious italics and bold scopes.

[ismell]

Oh this is awesome!

[aziz]

I you want some stats on what scopes are currently used check my tmtheme editor’s stats page
https://tmtheme-editor.herokuapp.com/#!/stats