This turns messages like:
```
** INFO: User plugins: /home/enrico/tmp/geany_conf/plugins/geanypy/plugins
** INFO: System plugins: /home/enrico/apps/share/geany/geanypy/plugins
```
into
```
GeanyPy-INFO: User plugins: /home/enrico/tmp/geany_conf/plugins/geanypy/plugins
GeanyPy-INFO: System plugins: /home/enrico/apps/share/geany/geanypy/plugins
```
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/371
-- Commit Summary --
* Set G_LOG_DOMAIN for proper GLib error reporting/logging
-- File Changes --
M geanypy/src/Makefile.am (3)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/371.patchhttps://github.com/geany/geany-plugins/pull/371.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/371
These are some patches related to the scope completion patch set:
1. The first patch is the scope completion for namespaces.
2. Then there's a patch using the langs_compatible() function for scintilla type colorization - this is a prerequisite of https://github.com/geany/geany/pull/857
3. When working on the above patch I noticed that the -1/-2 language type codes are a bit confusing and not used correctly in the function so I tried to clean it up a bit and fix things.
4. When testing scope completion for boost I noticed there are many tags with identical names (probably because of inheritance). Just one tag of the given name can be passed to Scintilla for tag colorization to improve performance a bit.
5. The very last patch is a suggestion but I can remove it if you find it too intrusive.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/906
-- Commit Summary --
* Add scope completion for namespaces
* Cleanup NONE/AUTO filetype definitions
* Use the langs_compatible() function when passing typenames to scintilla
* Don't pass multiple copies of identical type name to scintilla for colorization
* Don't use ctags types inside Geany
-- File Changes --
M src/editor.c (12)
M src/filetypes.c (2)
M src/filetypes.h (8)
M src/symbols.c (10)
M tagmanager/src/tm_parser.h (14)
M tagmanager/src/tm_source_file.c (23)
M tagmanager/src/tm_source_file.h (12)
M tagmanager/src/tm_tag.c (22)
M tagmanager/src/tm_tag.h (8)
M tagmanager/src/tm_workspace.c (108)
M tagmanager/src/tm_workspace.h (8)
-- Patch Links --
https://github.com/geany/geany/pull/906.patchhttps://github.com/geany/geany/pull/906.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/906
On Windows, I just built Geany and it failed because I had python-lxml not installed in MSYS2. Though even the configure check failed with an ImportError, `make` still tried to use the Python script.
Log output: http://pastebin.geany.org/TWdfm/
I'm wondering about:
```
checking for python lxml package... Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: No module named lxml
no
```
but then later on `configure` says: `Generate GtkDoc header : yes`.
Installing python-lxml is no problem, will do this but still wondering about failing compilation.
Either it is something Windows specific or the configure check might be wrong.
@kugel- ideas?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/929
Hi,
For professional needs, I'm using Geany for coding in COBOL. The filetype is pretty basic and I try to improve it by adding a secondary keywords declaration line and missing keywords.
But I have 2 issues : when I type only the character 'V' in a source I have the color of the numbers on it and all the keywords starting with V are not highlighted (like VALUE or VARYING). I think maybe 'V' is considered a roman numeral (although I don't have the same problems with 'I' or 'X').
Is anybody has an idea of the problem ?
Thank you in advance !
Best regards,
Franck
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/930
Fix "translatability" of several plugins, either overall (*GeanyCTags*, *DevHelp*, *GeanyMacro*, *Overview*), only the infos, and remove redundant localization init in some plugins.
Symptoms are that translation might not work in certain cases i.e. if the plugin is loaded first (or alone), or only one from GP installed.
*GeanyPy* also suffers from the non-translatability, but it doesn't have `LOCALEDIR` and `GETTEXT_PACKAGE`properly set from it's build system so it's not as straightforward to fix. @codebrainz
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/377
-- Commit Summary --
* Fix translatability of several plugins
* Remove redundant localization initialization
-- File Changes --
M devhelp/src/dhp-plugin.c (4)
M geanyctags/src/geanyctags.c (3)
M geanydoc/src/geanydoc.c (6)
M geanyextrasel/src/extrasel.c (4)
M geanyinsertnum/src/insertnum.c (4)
M geanylatex/src/geanylatex.c (2)
M geanylipsum/src/geanylipsum.c (2)
M geanymacro/src/geanymacro.c (5)
M geanyprj/src/geanyprj.c (6)
M geniuspaste/src/geniuspaste.c (1)
M overview/overview/overviewplugin.c (4)
M pretty-printer/src/PluginEntry.c (3)
M scope/src/scope.c (1)
M shiftcolumn/src/shiftcolumn.c (10)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/377.patchhttps://github.com/geany/geany-plugins/pull/377.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/377
Move all `@deprecated` stuff inside `GEANY_DISABLE_DEPRECATED` guards, and mark some with `G_GNUC_DEPRECATED` or G_GNUC_DEPRECATED_FOR`.
Apart that the code should not have been modified, but merely reordered.
Note: all PG seem to build just fine as of current master (e.g. not modified for the occasion).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/911
-- Commit Summary --
* Move deprecated declarations inside GEANY_DISABLE_DEPRECATED guards
* Mark deprecated API so GCC can warn about it
-- File Changes --
M src/plugindata.h (104)
M src/sciwrappers.h (8)
M src/ui_utils.h (7)
-- Patch Links --
https://github.com/geany/geany/pull/911.patchhttps://github.com/geany/geany/pull/911.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/911