Less Filewatcher Configuration Problem

I am having a problem when the Less plugin compiles the .less file

When it fails, I get this in the Project tree, where the .css file looks like a child of the .less file:

less-issue-1.png

The output shows errors and the .css file contains this kind of thing:

/Users/john/Sites/less/less-1.3.3.min.js: line 1: //: is a directory
/Users/john/Sites/less/less-1.3.3.min.js: line 2: //: is a directory
/Users/john/Sites/less/less-1.3.3.min.js: line 3: //: is a directory
/Users/john/Sites/less/less-1.3.3.min.js: line 4: //: is a directory
/Users/john/Sites/less/less-1.3.3.min.js: line 5: syntax error near unexpected token `('
/Users/john/Sites/less/less-1.3.3.min.js: line 5: `// Copyright (c) 2009-2013, Alexis Sellier'

I think it has something to do with how I have configuered the file watcher and / or less profile.  I'm not sure  Of course this error seems to be coming from the less-1.3.3.min.js file :

less-issue-2.png
and....

less-issue-3.png
If I turn off the file watcher and just use the compile less command from the flyout, seems to work fine  Maybe I don't understand what to use to compile with in the watcher?  Is the plugin providing it's own code that does the compiling? maybe it's a recursive issue with how the paths are configuered. How do I set up the watcher correctly?

Confused.

Thanks,

-John

2 comments

I changed "Output paths" to: "$FileDirName$/$FileNameWithoutExtension$.css" and it seems to be working better, but the console is still complaining.

I have read the docs, but I am unclear on all the terminology.  I am stil not certain I am doing this correctly.

-John

0

Hi there,

This is how I did it (and how it is intended to be done) -- works perfectly fine: http://devnet.jetbrains.com/message/5481646#5481646

It does not require any LESS plugg-in -- it's completely different thing/implementation.

P.S.
After installing some stuff (depends if IDE is running at that time) you may need to restart whole computer for some changes to become visible in IDE.

0

Please sign in to leave a comment.