1

Until today, I had been using Sublime Text 2 and WinLess software to compile .LESS files to CSS. The files got compiled automatically when I saved a file.

However since I upgraded to Sublime Text 3, automatic compiling has stopped. To see if its issue with WinLess, I tried editing the .less file in NotePad, and the automated compilation work.

So I am assuming Sublime Text3 seems to be locking file or something.

Anyone faced this or have any ideas to debug?

Harish Chouhan
  • 204
  • 2
  • 15

1 Answers1

2

Try adding the following to your Preferences (Preferences -> Settings-User):

"atomic_save": false

See this question and my answer below for an explanation of what Sublime is doing behind the scenes when atomic_save is true (the default setting). Temp files are created and destroyed, and the original file is deleted and recreated. This could easily mess with a LESS compiler just looking for a simple file modification. Using the "atomic_save": false setting also dramatically decreases save time on some network setups.

Community
  • 1
  • 1
MattDMo
  • 100,794
  • 21
  • 241
  • 231
  • Wow, that did it. Thanks mate. Really appreciate your help. Another question though (after reading your answers on the other thread). Has this feature been introduced only since version 3? Is there any major side affects after disabling? – Harish Chouhan Feb 08 '14 at 19:25
  • 1
    @HarishChouhan - yes, this was introduced in ST3. Theoretically, if something were to happen to the file during saving (such as another process trying to modify it) you could end up with a corrupted file if `atomic_save` is true. However, the chances of that are very slight, especially if you only have the file open in one place at a time, and you know other processes aren't using it. – MattDMo Feb 08 '14 at 23:29