Open core-ai-bot opened 3 years ago
Comment by AhoyLemon Tuesday Apr 28, 2015 at 20:17 GMT
:+1: Yes please. Sass is still folding as it should for me (as is JS & HTML), but I use jade a lot these days and it's a bummer to lose that ability.
Comment by labo-css Wednesday Apr 29, 2015 at 08:14 GMT
Scss syntax? I use sass syntax and it don't work. And jade... ^^'
Comment by prafulVaishnav Wednesday Apr 29, 2015 at 08:21 GMT
@
labo-css Can you please elaborate problem in code folding for sass. Is code-folding not working at all for sass file and working with js/html/css ?
Comment by labo-css Wednesday Apr 29, 2015 at 08:26 GMT
It work with css, html but not sass (sass syntax) & jade.
Comment by AhoyLemon Wednesday Apr 29, 2015 at 15:14 GMT
Oh yeah,@
labo-css is right. .scss
folds up nicely, but I made a little test document with the .sass
syntax and that one doesn't have any fold arrows. Couldn't confirm if .sass
used to work with the extension, as I've always used .scss
Comment by labo-css Wednesday Apr 29, 2015 at 16:27 GMT
Jade & Sass syntax worked well with the extension, and now i can't install it because it is not supposed to work with 1.3.
So... i'm screwed :D
Comment by thehogfather Wednesday Apr 29, 2015 at 22:25 GMT
@
labo-css the extension had the alwaysUseIndentFold
preference on by default. This preference is off by default in 1.3. In your .brackets.json
file (either at project or user level) create an entry for "code-folding.alwaysUseIndentFold": true
and your sass and jade files should get back the fold markers.
Be aware though that this will cause more fold markers to appear in your files - even plain text documents.
Comment by AhoyLemon Thursday Apr 30, 2015 at 00:46 GMT
Did that, jade is folding as expected now. The odd misinterpreted indentation is possible, but this solves way more problems than it creates, so thanks@
thehogfather.
Comment by labo-css Thursday Apr 30, 2015 at 05:03 GMT
Oh yeah thanx :+1: http://cdn.meme.am/instances/22489608.jpg
Issue by labo-css Tuesday Apr 28, 2015 at 07:56 GMT Originally opened as https://github.com/adobe/brackets/issues/11006
With the past solution (the plugin) they worked well. :/