Hello All,
I got a question about the translation files. If I have a translated
string like in the example below, does the comment with the source
location have a meaning for the translation tool or is it "only" an
information for other developers?
#. Windows
#: ../webhelper/src/gwh-plugin.c:541
msgid "Windows"
msgstr "Fenster"
Thanks for any answers in advance.
Greetings,
Lars
Hi!
I am writing D language plugin on D:
https://github.com/denizzzka/geany_dlang
This plugin isn't adds any new functionality but I planning replace already
implemented Geany functionality.
Especially, it will replace autocomplete list, tips list, symbol searching,
syntax highlighting by same D's infrastructural libraries calls.
Questions: It is possible to...
... intercept some Geany to Scintillia messages by a plugin?
(SCI_AUTOCSHOW, SCI_CALLTIPSHOW)
... replace call "Go to Symbol Definition"?
... fill out ctags info from external library instead of internal functions?
Thanks!
We are happy to announce a new version of the combined Geany-Plugins
release -- Following the Geany 1.31 release, Geany-Plugins 1.31 is being
released, too.
Some highlights:
* New plugin: keyrecord
* OS X: Use path relative to bundle to make plugins GeanyGenDoc,
GeniusPaste, GitChangebar, Overview, PoHelper, Scope work better on
Apple's operating system
* Windows: Fix crashes on GeanyExtrasel, GeanyLua, GeanyMacro,
GeanyNumbersBookmarks
* ProjectOrganizer: Fix a crash by ensuring project is open before
trying to expand the tree
* GitChangebar: Fix spurious line wrapping
* Updated translations: de, es, pt
A more complete list of changes can be found at NEWS at
https://github.com/geany/geany-plugins/releases/tag/1.31.0.
As usual, you can find source tarballs and Windows installer for the new
release on https://plugins.geany.org.
A huge thanks to everybody contributing to this great release.
Happy hacking!
We are happy to announce a new release of Geany!
For a comprehensive list of changes please see
https://www.geany.org/Documentation/ReleaseNotes.
Some highlights:
* Fix crash when a plugin calls plugin_set_key_group() more than once
(Jiří Techet).
* Fix updating statusbar after applying indentation detection.
* Fix converting color to hex for insertion in the Color Chooser dialog
(Vasiliy Faronov).
* Update Matlab, Haxe, Arduino, HTML, C# and CMake filetypes.
* Updated translations: ca, id, ja, kk, lt, ru.
We want to thank all developers, translators and everyone who
contributed to this release with patches, feedback, bug reports and
so on. Thank you!
As usual, all downloads can be found on
https://www.geany.org/Download/Releases.
Happy hacking,
Enrico
Hello everyone,
I'm Saurabh Mishra (IT student) from India.I've installed the recent
Geany from git. Actually, I'm new to open source and I found the
Geany project very interesting. And I really want to make some useful
contributions to Geany.
But, I do need some help regarding what Libraries should I learn?
If you can just guide me about this then it'll be very helpful.
Regards:
Saurabh Mishra
Hi all,
>From discussions elsewhere, such as [1], it sounds like one of the
things holding back Geany development right now is a need for more
testing.
I have some spare time that I can dedicate to exploratory testing of
PRs to Geany and Geany-Plugins. I'm not a QA professional, but I am a
programmer, I use a range of Geany features daily, and I understand
Geany's code.
How can I test PRs in a way that would really help them get merged?
In particular:
1. How can I determine that a PR is mostly blocked on testing, and is
likely to be merged when positive testing results come in? Some PRs
are marked as "approved" in GitHub yet are not merged -- is that it?
2. How can I communicate my results to the satisfaction of Geany
committers? For example, I could write up some kind of a report: an
outline of what I tried, with screenshots of what I got -- would that
help?
Thank you.
[1] https://github.com/geany/geany/pull/1246#issuecomment-290047712
--
Vasiliy