// out: null is auto-compiling my files
Closed this issue · 4 comments
// out: null is not working. It's auto-compiling set to out: null. This only happens when the file is first created. I noticed once I add to some less in these files, delete the css files that originally got compiled then the problem goes away.
Not sure I understand your problem. // out: null is currently not supported (it should create a file called null)
It doesn't create a file called null. If I add a less file and open it, it
creates a css version. I added out: null to the top saved and deleted the
css file and it keeps creating the css file. But once I add content to the
less file and then delete the css version it works. It works just letting
you know. What do you use if you don't want a file auto-compiled?
On Tue, May 24, 2016 at 7:04 AM Jonathan Diehl notifications@github.com
wrote:
Not sure I understand your problem. // out: null is currently not
supported (it should create a file call null)—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#89 (comment)
The compile.json typically helps
Okay thanks
On Wed, May 25, 2016 at 3:54 AM Jonathan Diehl notifications@github.com
wrote:
The compile.json typically helps
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#89 (comment)