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
This change makes the main window show immediately after launching Geany
so it's immediately visible Geany started. With big files/projects this
gives users better feedback about it's starting than not showing anything
until all the files are ready.
This is a separated patch suggested by @codebrainz in https://github.com/geany/geany/pull/576. It might be a bit risky for Geany 1.27 because plugins might make some assumptions when geany-startup-complete is called so this one might need some more testing. Possible candidate for early 1.28 merge.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/924
-- Commit Summary --
* Open files session files after entering main loop
-- File Changes --
M src/libmain.c (59)
-- Patch Links --
https://github.com/geany/geany/pull/924.patchhttps://github.com/geany/geany/pull/924.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/924
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
This eliminates some warnings with doxygen 1.8.7 on Ubuntu 14.04.4 LTS
based system. The default values of these options are equal to the
commented-out values so nothing should be broken by this change.
Without this I get
```
Warning: Tag `CLANG_ASSISTED_PARSING' at line 1034 of file `Doxyfile' belongs to an option that was not enabled at compile time.
To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u", or recompile doxygen with this feature enabled.
Warning: Tag `CLANG_OPTIONS' at line 1042 of file `Doxyfile' belongs to an option that was not enabled at compile time.
To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u", or recompile doxygen with this feature enabled.
Warning: ignoring unsupported tag `DOCBOOK_PROGRAMLISTING =' at line 1912, file Doxyfile
Warning: ignoring unsupported tag `PLANTUML_JAR_PATH =' at line 2339, file Doxyfile
```
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/925
-- Commit Summary --
* Comment-out some options not available on older doxygen versions
-- File Changes --
M doc/Doxyfile.in (8)
-- Patch Links --
https://github.com/geany/geany/pull/925.patchhttps://github.com/geany/geany/pull/925.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/925