I love Geany and use it all the time, but I was a little disappointed to find that CSS extension languages - such as Sass, SCSS and Less - do not have syntax highlighting
The userbase for these is probably small enough that new syntax highlighting rules specific to these languages would not be worthwhile, but to me it would make sense for the '.less' and '.scss' filename extensions to be recognised as CSS files (the same as '.css'); these languages are supersets of vanilla CSS (so the new features they add would still not receive highlighting, but most of the usual syntax highlighting one might expect would work)
Sass syntax is slightly different (uses indentation rather than braces a-la-Python) but still not a million miles from normal CSS.
You can set it yourself, just edit the `filetypes_extensions.conf` file (Menu->Tools->Configurations Files->filetype_extensions.conf` and add them to css. Don't forget to uncomment the line (and the [extensions] line near the top).
You can set it yourself, just edit the `filetypes_extensions.conf` file (Menu->Tools->Configurations Files->filetype_extensions.conf` and add them to css. Don't forget to uncomment the line (and the [extensions] line near the top).
@elextr Thanks very much for that; I wasn't aware of that file existing before. I've added .scss and .less as extensions for CSS files.
I still think it would be a good idea for them to be there by default but I'm glad they're configurable by the user (as now I can do more obscure things which really have no need at all to be in by default, such as giving game data which uses a standard markup format but a non-standard extension the appropriate highlighting)
I love Geany and use it all the time, but I was a bit disappointed to find that CSS extension languages - like Sass, SCSS and Less - don't have syntax highlighting.
@python-megapixel, I have the same problem as you when working with SASS/SCSS and LESS files, on Geany's [wiki](https://wiki.geany.org/config/scss) you can find the one for SASS, and although it uses the same CSS source type, you can configure some other things, like the compiler and a debugger.
For the moment I leave the [LESS](https://gist.github.com/diazvictor/f5170dc972eda6f06425ca5779f30cb4) one I have. follow the same steps as with the sass file to register this one.
I should also mention this patch for better support. http://geany.robert.dvu.pl/
i've manually adding the filetype.conf like in https://wiki.geany.org/config/scss for everytime i start over a new installation. I really wonder why aren't these files in the wiki be included in the filedefs by default? Just like the JSON filetype i think we have to manually add it but now it's included by default in the build
Hello,
I totally agree with @imakin. There was a discussion on this I started ca. a month ago, I'm adding here for reference: https://github.com/geany/geany/issues/3229 .
Sadly it seems the suggestion was heavily discarded.
@imakin I would say that the wiki files have not been added because nobody contributed to doing it, there was an attempt to make SCSS a first class filetype waaaay back in #20 and then a custom filetype #260 (which is pretty much the same as the wiki entry you linked), but nobody contributed to them so they didn't go anywhere, and now have bitrotted and have conflicts.
As I explained to @martonlente on #3229, everything in Geany is done by contributors, so if nobody contributes it, it won't happen.
github-comments@lists.geany.org