sublime-markdown-extended icon indicating copy to clipboard operation
sublime-markdown-extended copied to clipboard

Very strange console output

Open ghost opened this issue 9 years ago • 8 comments
trafficstars

Error loading scope:source.css.less: Unable to find syntax file for scope source.css.less in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.nginx: Unable to find syntax file for scope source.nginx in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.rust: Unable to find syntax file for scope source.rust in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.swift: Unable to find syntax file for scope source.swift in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.livescript: Unable to find syntax file for scope source.livescript in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.jade: Unable to find syntax file for scope source.jade in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.ejs: Unable to find syntax file for scope source.ejs in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.julia: Unable to find syntax file for scope source.julia in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.coffee: Unable to find syntax file for scope source.coffee in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.scss: Unable to find syntax file for scope source.scss in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.stylus: Unable to find syntax file for scope source.stylus in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.pgsql: Unable to find syntax file for scope source.pgsql in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:text.html.swig: Unable to find syntax file for scope text.html.swig in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

no such context scope:text.html.handlebars#.tag-generic-attribute in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

Error loading scope:source.postscript: Unable to find syntax file for scope source.postscript in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

rule #anon_latex_0 has a scope name, but is unreachable, so the name will never be used

rule #anon_latex_1 has a scope name, but is unreachable, so the name will never be used

ghost avatar Apr 21 '16 09:04 ghost

It is because Markdown Extended was trying to import some syntaxes which were not installed in your setup. It also makes Sublime Text 3114 very slow in rendering Markdown files. Possibly due to the new synta x highlighting engine?

randy3k avatar May 25 '16 06:05 randy3k

I have same problem. Output, when I start Sublime Text 3 and in Sublime Text 3 is open any markdown file:

startup time: 0.309898
first paint time: 0.341898
first paint time: 0.341898
Error loading scope:source.swift: Unable to find syntax file for scope source.swift in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.less: Unable to find syntax file for scope source.less in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.ts: Unable to find syntax file for scope source.ts in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.scheme: Unable to find syntax file for scope source.scheme in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.coffee: Unable to find syntax file for scope source.coffee in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.scss: Unable to find syntax file for scope source.scss in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.tsx: Unable to find syntax file for scope source.tsx in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.sass: Unable to find syntax file for scope source.sass in Packages/MarkdownEditing/Markdown.tmLanguage
Error loading scope:source.postscript: Unable to find syntax file for scope source.postscript in Packages/MarkdownEditing/Markdown.tmLanguage

If in Sublime Text no open markdown file, these lines are not displayed.

Thanks.

Kristinita avatar Sep 08 '16 17:09 Kristinita

Also mentioned in #180.

Both issues should be closed because it's an expected behavior and we can't - as sad as it it, avoid the clutter:

felixhao28:

Just for anyone who wonders about error messages like "Unable to find syntax file for scope source.swift", those are expected since those syntax definitions are optionally required. @maliayas and I talked about this here #174.

wbond:

The "annoying" errors are correct, and won't go away. The syntax is trying to include files you don't have, so it is warning you that the syntax is not going to work as originally intended because files are missing off of your system.

patrickwelker avatar Jul 06 '18 09:07 patrickwelker

So, are you saying that we should install all these languages, instead of :

  • Proposing settings options for the package, allowing us to manually disable collateral languages processed ?
  • Even better : improving the package to automatically disable syntaxes that it can't find during installation ?

Is that the way developers work in 2018 ? ^^ By the way, I've managed to install the first language missing (Swift), but I'm stuck with the second one (Coffee) : I don't find any package related to such a langage syntax, except many specific things.

Heraes-git avatar Jul 17 '18 13:07 Heraes-git

@Romarain It's CoffeeScrip, the once young and hot stepdaughter of JavaScript.

I hope, too, that this could be "fixed", but I totally understand if the author has better things to do. Then again I'm not totally sure if it can be fixed since already a lot of talented contributors to the package scene - including @wbond - looked at this problems from different angles.

patrickwelker avatar Jul 17 '18 14:07 patrickwelker

I kick this annoying msg box away by downloading this file https://raw.githubusercontent.com/sublimehq/Packages/master/Markdown/Markdown.sublime-syntax and put it into the folder Preferences->Browser Packages...

2bdenny avatar Jul 26 '18 07:07 2bdenny

I am unable to find appropriate packages for the following scopes:

  • source.css.less
  • scope:source.jade
  • scope:source.ejs
  • scope:source.julia
  • scope:text.html.swig

I've tried several syntax highlighting packages for less, jade, ejs and julia; I can't find any that make those loading errors go away.

For Swig, when I install the package by the same name, instead of

Error loading scope:text.html.swig

I get this:

no such context scope:text.html.swig#.tag_id_attribute in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax
no such context scope:text.html.swig#.tag_id_attribute in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax
no such context scope:text.html.swig#.tag_id_attribute in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax
no such context scope:text.html.swig#.embedded-code in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax
no such context scope:text.html.swig#.tag_id_attribute in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax
no such context scope:text.html.swig#.tag_id_attribute in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax
no such context scope:text.html.swig#.tag_id_attribute in Packages/Markdown Extended/Syntaxes/Markdown Extended.sublime-syntax

If anyone has resolved any of these, can you tell me the exact package name I should install? Thanks!

techrah avatar Dec 24 '18 21:12 techrah

Having the same issue.

Interestingly, MarkdownEditing (Packagecontrol link) doesn't have this problem.

The difference appears to be in the syntax definitions for fenced raw code blocks. MarkdownEditing uses embed whilst MarkdownExtended uses include ... does that make a difference?

As a user, I can see (or at least think I can see) the latency as all the errors get reported with MarkdownExtended but not with MarkdownEditing.

maegul avatar Oct 03 '20 12:10 maegul