>From discussions elsewhere, such as , it sounds like one of the
things holding back Geany development right now is a need for more
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
How can I test PRs in a way that would really help them get merged?
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
my name is Attila from Hungary. My profession is electronic mechancian,
but my job is C/C++ developer nowadays. You can look at my LinkedIn
https://www.linkedin.com/in/attila-v%C3%A9ghelyi-31597551/, and you
can visit my home page too: http://veghelyiattila.hu
I'd like to add a new feature to geany, because it's very lack for me.
This is the 'Reaload all', which is very usefull i.e. when I change the
git branch in the background terminal (and many files are open).
The code is almost ready (there is no code, which is totally ready :) ),
I must try it on Windows for example.
Geany having failed at being a small fast lightweight IDE and having
become a chubby middle aged application, its time for a re-think, a
new direction, a fresh start.
Instead it is proposed that Geany embrace the paradigms of the most
successful IDEs (like Emacs or Eclipse) and make coding with Geany
So looking at those things that are common to Emacs and Eclipse I propose:
1) Geany should change its name to start with an E, that is obviously
2) Eeany should embrace the bloat, incorporate the whole operating
system like Emacs and become an overblown interfering annoyance like
3) clearly using common UI conventions is important (to Eclipse) but
using custom paradigms is important (to Emacs) so it is proposed that
Eeany alternate between using normal keybindings and using randomly
selected sequences of keys. This will make editing an adventure again
as you struggle to find the "undo" sequence.
4) Geany is far too fast, so Eeany should incorporate code to perform
bitcoin mining between keystrokes, nobody will notice, and the devs
will get rich,
5) of course great software is not just Emacs and Eclipse, so Eeany
should copy the most important of the paradigms of great software,
phoning home with copious user data which can be sold, again making
the devs rich, and clearly this should be done in secret without any
ability to cancel it, using a spawned process that continues after
Eeany exits (and restarts on boot) without any way of preventing it,
6) having gotten all that data it is of course essential that it be
used, so Eeany must incorporate ads, a short video selling insurance
before the compile results display, tooltips suggesting a new
toothpaste to help clean both your code and your smile.
I'm sure everybody will support this initiative to put Eeany where it
belongs in the universe of code development, at the top*.
* YMMV, press release issued 1 April 2017