jonschlinkert / sublime-markdown-extended

Top 100 Sublime Text plugin! Markdown syntax highlighter for Sublime Text, with extended support for GFM fenced code blocks, with language-specific syntax highlighting. YAML Front Matter. Works with ST2/ST3. Goes great with Assemble.
https://github.com/jonschlinkert
MIT License
660 stars 96 forks source link

Very strange console output #125

Open ghost opened 8 years ago

ghost commented 8 years ago

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

randy3k commented 8 years ago

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?

Kristinita commented 7 years ago

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.

patrickwelker commented 6 years ago

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.

Heraes-git commented 5 years ago

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

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.

patrickwelker commented 5 years ago

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

2bdenny commented 5 years ago

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

techrah commented 5 years ago

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

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!

maegul commented 3 years ago

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.