I installed less with sudo npm install -g less
Here are the last 10 lines of output:
npm http 304 https://registry.npmjs.org/ctype/0.5.2 npm http 304 https://registry.npmjs.org/asn1/0.1.11 npm WARN package.json email@example.com No repository field. /usr/bin/lessc -> /usr/lib/node_modules/less/bin/lessc npm WARN package.json firstname.lastname@example.org No repository field. email@example.com /usr/lib/node_modules/less ├── firstname.lastname@example.org ├── email@example.com ├── firstname.lastname@example.org └── email@example.com (firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org)
Browed here a bit and figured maybe those warnings weren't the issue. Seemed all well and good, except when I run lessc without parameters it just kicks me back to the command prompt. Unusual as lesscss.org states this should list options. Same behavior when I try a command like
lessc less/style.less > css/style.css
Just kicks me back to the command line as if I never tried to execute anything. Expected a "command not found" at the very least. style.css remains uncompiled.
Background: I'm recently new to Ubuntu after a lot of time on OS X. I was used to LiveReload, but I still haven't wrapped my head around guard-livereload I figured I wouldn't mind doing some manual compiling for a little while.
Update: I started from scratch and built from source. Instructions to build from source: https://gist.github.com/dwayne/2983873 lessc works fine now after reinstalling from npm. I feel like I must have had some sort of conflict via apt-get somehow.
I've encountered this in the past and solved it by adding a symlink to a directory on my path:
sudo ln -s /usr/lib/node_modules/less/bin/lessc /usr/local/bin/lessc
I see you've worked around your issue, but someone else may find this information useful.
There is currently no discussion for this recipe.
This recipe can be found in it's original form on Stack Over Flow.