Hacker News Reader

Comment by dminor | Hacker News Reader

> Removed all color variables (e.g., @blue, @orange, etc). New, more meaningful variables are on their way (such as @state-warning-text).

Hooray! Should make customization that much easier.

View on HN

I'm sorry, I don't know what @state-warning-text is, googling it only seems to point to this article, could somebody explain please? thanks!

It was just an example, but what this means is that they are switching to semantic naming, rather than style naming.

The problem is that a variable name like "orange" is a very bad variable name in case your design wants warnings to be in, say purple for whatever reason.

If the LESS variable is called "state-warning-text", you can define that to be purple without the bad aftertaste of having to use "orange" when you mean purple.

Thanks!

I don't mind haveing color variables. When I need a new red, I define @projectRed or @redAlt. It is so much easier to remember red than some dangerColor.

Why will they choose hyphenated variables instead of camelCase?

>Why will they choose hyphenated variables instead of camelCase?

Presumably because hyphentation is the standard in CSS.

But, variables are not standard in CSS. I always perceived less variables as JavaScript variables.

Now, I need to figure out a way to make Vim treat hyphenated words as words for filetype=less.

You can either use the 'W' movement (instead of 'w') or use the 'iskeyword' option to change what is considered a word character. Word movement: http://vimdoc.sourceforge.net/htmldoc/usr_03.html#03.1

I enjoy having colour variables at the top that are project specific blues or oranges which can then be set as the values of other variables such as @state-warning-text.

Reply on news.ycombinator.com