Luke Page

One thought.. Matthews solution doesn't allow you to have a mixin (with unknown inheritance) and just work within your current selectors (as in #1158). Is it too complicated to have...

in a selector you have lots of pseudo classes using brackets and then you have variable substitution which borrows its syntax from the more verbose ~"@{var}" so for me normal...

@Smolations that came up in a different issue. We thought that this might be done using guards on css rulsets combined with being able to test parent selectors in the...

here https://github.com/cloudhead/less.js/issues/1174 for every feature we like to make sure it has real value-add.. if it makes it easier to not refactor your css to a better structure then it...

note - to implement the extend syntax options we will need to add a rule that the basics of the original request.. e.g. to escape the current nesting. We don't...

so presumably you assign a selector to a variable and then if you need that in a selector, you use the variable.. I like that it doesn't further complicate the...

``` @a:~".c"; @{a}.b { & + & { .d(nth(&, 1)); } } ``` take the above example.. We do this 1. call .d 2. evaluate @{a}.b 3. work out &...

I would expect for it to be useful, for & to equal the final selector, as it does when used as part of selectors.

this issue seems to have confused both the original one and the issue with bounding boxes of the svg. using `fontforge` the only issues I had with bounding box were...

I'm sorry, but no idea what the problem is, how to fix it.