-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide more information on less compilation error #1102
Comments
What does the (detailed) message say in Error List (Ctrl + W, E)? |
There are no detailed messages in Error List. |
Then unfortunately, there is nothing we can do about it. LESS compiler returns those errors. For instance, if you miss a closing parenthesis, it would say "ParseError: missing closing The entries in the error list will then show you the same messages, with line and column number. Double-click the message and it will highlight the line where the error occurred. Also, LESS editor will underline the erroneous syntax for you. |
That is the problem - there's no messages in error window and LESS editor has not underlined anything. And it compiles fine under another compiler. |
Can you share the contents of your LESS file via http://gist.github.com or http://pastebin.com? |
I'll try to isolate smaller piece, that is causing a problem, now it is quite big file. |
and gist to reproduce: https://gist.github.com/dziedrius/fbccc76d0f875a66e477 |
Compiler: Getting back errors in list (#1102)
This is fixed. |
That was quick, thanks a lot! |
I have a .less file and web essentials can't compile it, fails with:
/*
Compilation Error.
See error list for details
ParseError: Unrecognised input
*/
The same error was, when I was using wrong sequence of imports, but current file has no imports, web essentials see no errors in that file, so I can just guess what is happening.
May be it would be possible to output somewhere compiler command line that is used to compile current file, that I could copy to my console run.
Version is 2.1.2 (although in visual studio > about it is 1.0)
The text was updated successfully, but these errors were encountered: