Parse Error with Twitter Bootstrap 2.3.0

[francoispluchino]

An error is obtained with the new version of Twitter Bootstrap (2.3.0).

The compiler stops in mixins.less on line 578.

[SteveX]

Seeing this on 2.3.0, also 3.0.0. Replacing with lines from mixins.less 2.2.2 allows parsing to continue.
(~".span@{index}") { .span(@index); } //.span@{index} { .span(@index); } // parse error: line:578 (~".offset@{index}") { .offset(@index); } //.offset@{index} { .offset(@index); } // parse error: line:584 (~".span@{index}") { .span(@index); } //.span@{index} { .span(@index); } // parse error: line:623 (~'.offset@{index}') { .offset(@index); } //.offset@{index} { .offset(@index); } // parse error: line:629 (~"input.span@{index}, textarea.span@{index}, .uneditable-input.span@{index}") { .span(@index); } // input.span@{index}, textarea.span@{index}, .uneditable-input.span@{index} { .span(@index); } // parse error: line:678

[francoispluchino]

That is a temporary edit. I use Composer and Twitter Bootstrap is in my vendors directory, so whenever there is an update, the changes are deleted.

However, the error comes from a new Selector Interpolation added in Less 1.3.1.
It would be cool to add this new selector.

[SteveX]

Yes, very much temporary.

You might not get a parse error but to SteveX's fix above you should also replace line 630 with:
(~'.offset@{index}:first-child') { .offsetFirstChild(@index); } // .offset@{index}:first-child { .offsetFirstChild(@index); }

If you don't do the above you get layout issues because all the fluid grid definitions like below get messed up. I am sure it affects other places as well.
.row-fluid .offset12 {
margin-left: 104.25531914894%;
*margin-left: 104.14893617021%;
}
.row-fluid :first-child {
margin-left: 102.12765957447%;
*margin-left: 102.02127659574%;
}
SHOULD BE
.row-fluid .offset12 {
margin-left: 104.25531914894%;
*margin-left: 104.14893617021%;
}
.row-fluid .offset:first-child {
margin-left: 102.12765957447%;
*margin-left: 102.02127659574%;
}

[francoispluchino]

Is the repository always maintained? Or is it better that I change by installing a node.js?

[jackmoore]

You should absolutely choose node if that is an option. It doesn't really matter how well maintained this repository is, the official translator is provided as a node package which will always be preferred over 3rd party ports.

[leafo]

Pushed support to master.

[barryvdh]

Seems to be working fine so far, thanks!. Maybe tag a new release so Bootstrap works when updating with composer or downloading from the site?

[dmyers]

@leafo +1 for tag release

[leafo]

Sorry for delay, it's out http://leafo.net/lessphp/changelog.html