Sergey Chikuyonok
Sergey Chikuyonok
@banderazz no, your comment isn’t hateful, I love user’s feedback, even it tells that I doing something wrong :) Here’s what I think about it. I’ve created LiveStyle because every...
Please post console log of ST: https://github.com/emmetio/livestyle-sublime/blob/master/messages/install.txt
Can you post an example of such file? ST3 shouldn’t slow down here because it doesn’t do any calculations, it only sends data to Chrome
The general solution is to send `calculate-diff` message and then wait for incoming `diff` message which means current payload was calculated. In-between `calculate-diff`—`diff` any `on_modified` editor events must simply tell...
See https://github.com/livestyle/client#events-reference for event reference
LiveStyle never commented out rules. It’s pretty complex behaviour to implement. Anyway, I think about it.
This is Chrome DevTools feature. Anyway, I agree it’s a big issue so I’ll think about it
> Emmet LiveStyle: [client] Invalid CSS structure Your CSS is invalid
Please provide debug log: https://github.com/emmetio/livestyle-sublime/blob/master/messages/install.txt
You should download extension (Right click on link > Save Link As) and then drag’n’drop downloaded file