See for instance what VLC does. (Or Audacity for that matter.)
Geany’s feature set is large enough (let alone accounting for
plugins) that it may warrant such an enhancement.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2848
In the Documentation generator menu the manual links to ```/usr/share/doc/geany-plugins/geanygendoc/html/manual.html``` and not ```/usr/share/doc/geany-plugin-gendoc/manual.html```.
This is in Geany 1.33-1 on Debian 10 (buster) in XFCE 4.12.5.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/992
I went through the various open PRs and open issues providing/requesting support of certain languages because some seem to be a bit neglected:
1. There's this PR adding Prolog support.
2. There's the Raku language support in #3169 which is hopefully in a mergable state.
3. I created #3647 (Scintilla lexer for JSON) and #3648 (Scintilla lexer for Nim) - for JSON there has already been a pull request in the past and they have also been requested in some open issues and in general I agree that when there's a Scintilla lexer, we should use it.
4. Yesterday I reviewed #3480 (CIL language support) and if the minor comments I had get addresses, I think it should be merged.
5. There are various open PRs and issues asking for Dart, LESS, and SCSS - these could be added as external filetypes. There should be no problem using C lexer for Dart and CSS lexer for LESS/SCSS (the CSS lexer supports LESS/SCSS modes).
What do you think?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3651
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3651(a)github.com>
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 are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2767
In ~/.config/geany/filetype_extensions.conf this could be added by default:
`CSS=*.css;*.less;`
In ~/.config/geany/filedefs/filetypes.css this could be added by default:
```
[lexer_properties]
lexer.css.less.language=1
```
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1626
TOML is a fairly strictly defined configuration file syntax, used by various projects, supported by plenty of languages and already supported by some editors. I'm not familar with geany plugin dev (and lacking the time anyway) but maybe someone's interested in creating a syntax highlighting ruleset, similar to the INI config format.
https://github.com/toml-lang/toml
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1268
Is it possible? I set up my favorite color scheme for the editor, but the rest of UI is very bright "black-on-white".
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2928