Sublime Forum

Dev Build 3088

#1

Dev Build 3088 is out now, addressing some syntax regressions in 3087.

What’s not fixed is overriding the JavaScript syntax definition with a tmLanguage file. It 3088, it’s possible to override JavaScript.sublime-syntax, by making another file called JavaScript.sublime-syntax in a folder that is lexicographically ordered after ‘JavaScript’.

I’d like to allow tmLanguage files to be used to override JavaScript.sublime-syntax, but the best approach needs to be pondered some more.

1 Like
#2

Since yesterday I’ve had all Markdown tmLanguage files (both the default and the one provided by MarkdownEditing) choke with the following error:

error: Error loading syntax file "Packages/Markdown/Markdown.tmLanguage": Unable to find CSS.sublime-syntax

The problem began with yesterday’s build (3087) but persists in this one. Ideas?

0 Likes
#3

A bug with Goto Anything. When I type “SomeClass@create” a list will be populated with methods from SomeClass that start with “create” but no matter which one I choose Sublime will open the first one from the list.

0 Likes
#4

Sounds like you have the CSS package in the ignored packages list.

0 Likes
#5

To clarify on this, if I have the following two files:

Packages/JavaScript/JavaScript.sublime-syntax
Installed Packages/JavaScript 2.sublime-package/JavaScript.sublime-syntax

and another file, i.e. HTML.sublime-syntax, includes a file named “Packages/JavaScript/JavaScript.sublime-syntax” it will in fact include “Installed Packages/JavaScript 2.sublime-package/JavaScript.sublime-syntax”?
And if the second file was named as “Installed Packages/Better JavaScript.sublime-package/JavaScript.sublime-syntax” it would use the default file?

0 Likes
#6

The highlight at oneline php tags was fixed, but I noticed PHP snippets aren’t working inside them.

I fixed it by adding - meta_content_scope: source.php after line 34 at PHP.sublime-syntax.

[pre=#272822]— PHP.sublime-syntax
+++ PHP.sublime-syntax
@@ -32,6 +32,7 @@
0: punctuation.section.embedded.begin.php
push:
- meta_scope: meta.embedded.line.php

  •        - meta_content_scope: source.php
       - match: (\?)>
         captures:
           0: punctuation.section.embedded.end.php[/pre]
0 Likes
#7

There is still the issue about the Goto Definition, when you have multiple groups: it will always open the file in your current group even if it is already open in another group. You end up with the same file open multiple times …
This “regression” was introduced a few release ago, I can’t remember exactly which version.

0 Likes
#8

Thanks! I did because I was using a third-party CSS package. I disabled it and enabled the default package and everything is dandy :smile:

0 Likes
#9

This seems like the right place to post a bug introduced by this build. (I am new here. Please direct me to the right place if I am wrong.)

In vintage mode, “o” and “O” (to enter insert mode on the line above/below) seem to be broken. They enter insert mode on the current line instead.

0 Likes
#10

[quote=“Clams”]There is still the issue about the Goto Definition, when you have multiple groups: it will always open the file in your current group even if it is already open in another group. You end up with the same file open multiple times …
This “regression” was introduced a few release ago, I can’t remember exactly which version.[/quote]

I think this change was more or less intentionally. See github.com/SublimeTextIssues/Core/issues/311 for some discussion. (Basically, the issue is that previewing in the same group as the panel is visible is a must, but then opening the file in a different group is not exactly intuitive.)

0 Likes
#11

In this case it would be really nice if this was configurable: i find the new behavior a lot more annoying than whatever edge effect the previous behavior had. Handling a lot of tab is not the strong point of Sublime :wink:

0 Likes
#12

Thanks for the report, this is now fixed is 3090

To clarify on this, if I have the following two files:

Packages/JavaScript/JavaScript.sublime-syntax
Installed Packages/JavaScript 2.sublime-package/JavaScript.sublime-syntax

and another file, i.e. HTML.sublime-syntax, includes a file named “Packages/JavaScript/JavaScript.sublime-syntax” it will in fact include “Installed Packages/JavaScript 2.sublime-package/JavaScript.sublime-syntax”?
And if the second file was named as “Installed Packages/Better JavaScript.sublime-package/JavaScript.sublime-syntax” it would use the default file?
That’s correct.

Thanks, fixed in 3090

[quote=“Clams”]There is still the issue about the Goto Definition, when you have multiple groups: it will always open the file in your current group even if it is already open in another group. You end up with the same file open multiple times …
This “regression” was introduced a few release ago, I can’t remember exactly which version.[/quote]

That was a deliberate change to bring things into line with Goto Anything, which has always operated this way.

0 Likes