zmoazeni/csscss

Output in Windows

Closed this issue · 6 comments

lucascosta commented

{←[0;31;49m#comments←[0m} AND {←[0;31;49m.page-template-default #content .hentry
, .page-template-template-fullwidth-php #content .hentry,
.single #content .hentry←[0m} share ←[0;31;49m6←[0m rules

peterkeating commented

Same as #11.

ptashka-berkut commented

Same here when tried using
ruby 1.9.3p362 (2012-12-25) [i386-mingw32] on Windows 8

Regular output:
{←[0;31;49m.lineIndicator←[0m} AND {←[0;31;49mdt.dispositionsWarn←[0m} share ←[0;31;49m3←[0m rules

Verbose output:
{←[0;31;49m.lineIndicator←[0m} AND {←[0;31;49mdt.dispositionsWarn←[0m} share ←[0;31;49m3←[0m rules
-- ←[0;33;49mcolor: #fff←[0m
-- ←[0;33;49mfont-weight: 400←[0m
-- ←[0;33;49mpadding-bottom: 5px←[0m

HOWEVER, when I tried the same using
ruby 2.0.0p0 (2013-02-24) [x64-mingw32] on Windows 8 - IT WORKED!

Regular output:
{.lineIndicator} AND {dt.dispositionsWarn} share 3 rules

Verbose output:
{.lineIndicator} AND {dt.dispositionsWarn} share 3 rules
-- color: #fff
-- font-weight: 400
-- padding-bottom: 5px

CSS selectors were highlighted in red and CSS rules - in yellow.

AWESOME!

zmoazeni commented

Also similar to #44 - I should probably disable POSIX coloring by default on windows.

@ptashka-berkut I'm confused though. Are you saying that it behaved differently due to 1.9.3 vs 2.0.0? Or was something else different in the 2nd windows test? That kind of changes my perspective on the issue.

ptashka-berkut commented

As far as I understand there was only one difference between the 2 test cases.
First tried it in 1.9.3, then tried it in 2.0.0. Same machine and everything else. The machine is 64 bit, if that makes a difference.

Thanks for this cool gem, BTW!

zmoazeni commented

Thanks! I'll disable color by default on windows < 2.0 for now, and see where that gets us. 2.0 may magically fix this, though that seems odd.

zmoazeni commented

This is now in master and will go out in the next release. Sorry about the gibberish.