Geany is "ok".
There are a few things to be fixed, like how it handles files in a C-project.
Only absolute path? That makes it very annoying - because you lose the project references - when you move the project. I fixed/hacked to relative path.
[files]
current_page=3
FILE_NAME_0=/mnt/src/machine/platform/arm/zaurus/bootloader/src/v5/app.c
(not modified version of geany)
[files]
current_page=3
FILE_NAME_0=./app.c
(modified version of geany)
The geany project file needs to be autogenerated in order to have the right directives { all, clean, clean_all, interfaces, run, test, ... } to your Makefile.
[build-menu]
CFT_00_LB=_Compile
CFT_00_CM=make
CFT_00_WD=
CFT_01_LB=_Build
CFT_01_CM=make clean_all; make interfaces; make
CFT_01_WD=
filetypes=C;
EX_00_LB=_Execute
EX_00_CM=make run
EX_00_WD=
Not a problem, you just need to write a script for this.
The real big problem is how the geany interface is written: gtk-xml is very complex if you need to add/remove/change a button, e.g. { do
bg, ice, autoindent, coverage, ... }.
Plus, see
here, supporting Markdown needs external plug-in, which are problematic to be compiled, especially on { mips32, hppa, ppc32 ... }