-
Notifications
You must be signed in to change notification settings - Fork 155
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
Errors #9
Comments
Thanks for all the great feedback! I'll try incorporating some of them soon. |
Hi Zach, I get a whole bunch of syntax errors when running this: /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in Any help appreciated - thanks. |
@nilsborchers Yeah 1.8.7 isn't supported only 1.9.x+ |
hmm ok i updated to 1.9.3 now and am getting similar stuff:
|
@nilsborchers Let's move this conversation to #11. In fact this comment might be helpful to you. |
@zmoazeni ahh thx you're right i had to uninstall the 1.8 gem and reinstall with the new gem bin :) |
@nilsborchers How did you uninstall the 1.8 gem after installing 1.9? |
@kevboutin Can we keep 1.8 vs 1.9 issues in #11? You can tag him in that thread as well. |
@ahmedelgabri Ok a couple fixes just hit master and will be released in the next version (after v1.0.0)
This is now
This is fixed in master too. I can't be 100% accurate but at least it's closer than the useless "line: 1, column: 1" all the time. I'm going to close this issue and reopen a different one that is solely about line numbers. |
@zmoazeni This is great, Looking forward for the new release. On Fri, Apr 12, 2013 at 7:52, Zach Moazeni <notifications@github.com="mailto:notifications@github.com">> wrote: I would prefer if the debug feature is a flag something like --debug or --debug=true instead cause when I wrote this csscss --help it didn't say anything about how can I turn debug on. This is now --show-parser-errors Had a problem parsing the css at line: 1, column: 1 ...The problem actually was at line 1964. This is fixed in master too. I can't be 100% accurate but at least it's closer than the useless "line: 1, column: 1" all the time. I'm going to close this issue and reopen a different one that is solely about line numbers. — |
All set in v1.1.0. Sent from my iPhone On Apr 12, 2013, at 2:15 AM, Ahmed El Gabri notifications@github.com wrote:
|
I have some feedback on the error messages.
After installing it & I was debugging an old CSS file & I got this error
I runned
csscss -v body.css
I got this `Had a problem parsing the css at line: 1, column: 1Run with CSSCSS_DEBUG=true for verbose parser errors'
I would prefer if the debug feature is a flag something like
--debug
or--debug=true
instead cause when I wrote thiscsscss --help
it didn't say anything about how can I turn debug on.secondly, after I tweeted you & you replied back that I need to run the command like this
CSSCSS_DEBUG=true csscss -v body.css
I got another errorHad a problem parsing the css at line: 1, column: 1 Failed to match sequence (SPACE? blocks:((COMMENT / NESTED_RULESET / RULESET) {1, }) SPACE?) at line 1957 char 1. - Don't know what to do with "p.contactu" at line 1957 char 1.
actually the selector was
p.contactussubheading
excuse the bad selector name, apparently that's why I needed this tool so I can debug this file :) The problem actually was at line 1964.Lastly, I think the output will be very helpful if it has line numbers, right now it looks like this
{.selector} AND {#selector} share 10 rules -moz-border-radius: 2px 0px 0px 2px another: rule; another-rule; ...
Maybe something like this will be better
L:20 {.selector} AND L:45 {#selector} share 10 rules -moz-border-radius: 2px 0px 0px 2px another: rule; another-rule; ...
The text was updated successfully, but these errors were encountered: