Standard gettext should be used over glib's glue these days.
AM_GLIB_GNU_GETTEXT and glib-gettextize are deprecated. This helps
possible meson build (no concrete plans yet) as well as working with
intltool is harder over there. gettext, on the other hand, is supported
out of the box in meson.
Beware, autopoint is a new dependency when building from git,
should not affect tarballs. Also, it's already required by Geany core.
Additionally, autogen.sh follows Geany's autogen.sh more closely,
allowing for out-of-tree builds.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1183
-- Commit Summary --
* Use standard gettext, following Geany core.
* Fix issues found by standard gettext
* Update po files after gettext transition.
-- File Changes --
M .github/workflows/build.yml (1)
M .gitignore (7)
M autogen.sh (11)
M build/common.m4 (1)
M build/i18n.m4 (10)
M configure.ac (8)
A po/LINGUAS (1)
A po/Makevars (82)
M po/POTFILES.in (8)
M po/be.po (710)
M po/ca.po (771)
M po/da.po (697)
M po/de.po (966)
M po/el.po (690)
M po/es.po (952)
M po/fr.po (950)
M po/gl.po (780)
M po/it.po (847)
M po/ja.po (770)
M po/kk.po (720)
M po/nl.po (812)
M po/pt.po (0)
M po/pt_BR.po (0)
M po/ru.po (0)
M po/tr.po (0)
M po/uk.po (0)
M po/zh_CN.po (0)
M treebrowser/src/treebrowser.c (0)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1183.patchhttps://github.com/geany/geany-plugins/pull/1183.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1183
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1183(a)github.com>
Hey guys, for those who using Geany on Windows OS and want a dark theme ui like monokai theme, you can just clone my repo [Geany-WebDev-Snippets](https://github.com/zhaolinlau/Geany-WebDev-Snippets) and go to `Geany-WebDev-Snippets -> themes -> monokai`, then drag the whole `gtk-3.0` folder to your `C:\Users\Win10\AppData\Local`.
After that, your Geany will be transform from this
to this
And I will add more themes to my repo in the future.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3283
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3283(a)github.com>
Are there any plans to add support of lsp to Geany?
--
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/2184
Hi.
I would like to have a button or shortcut that lets me filter the files I see in the open file pane by pressing the first letter. I have ~1000 files open and I am very happy to see that the editor can handle that many files I just need a bit of help from the UI in order to jump to the right file.
Thank you for creating the best editor for coding in Vala.
Cheers
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3078
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3078(a)github.com>
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
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
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