GeanyLatex and "Make": Shortcuts become disabled about geany-plugins HOT 4 OPEN

Is only the Make-menu-item effected by this? Do you see any output in Debug (Help->Debug) or while starting Geany from prompt?

from geany-plugins.

All "Make" menu-items are affected when the bug is triggered.

I will look at Help->Debug the next time this happens. For the record, in the current run (where the bug hasn't triggered yet), I see several "INFO" lines, so Help->Debug works and there do not seem to be any warning or errors so far.

I always start Geany from a command-line, and never see any warnings or errors. I am not sure which application causes the following warning (a standard warning that seems to be aimed at certain GTK-devs), so it may or may not be Geany.

(process:31772): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

EDIT: Googled and explained the warning

from geany-plugins.

I believe I found the core issue: geany really doesn't like Makefiles that spawn daemons, e.g. contain a target that executes program & or similar.

Workaround: as soon as the called program returns, geany can make again. In my case it's evince, which exits immediately if there already is another instance running (which then reloads the PDF in question), so this is very easy for me.

However, I believe that Geany should be able to make again as soon as make returns, so I do consider this a bug.

from geany-plugins.

However, I believe that Geany should be able to make again as soon as make returns, so I do consider this a bug.

I don't think so. I'm not so much knowledgeable about that, but AFAIK for the background jobs not to block Geany's spawning, it would require for Geany to inherit those children from the process it spawned, as they didn't deamonize themselves and need a parent.
I don't know what Geany could even do (portably, nonetheless) to achieve that, but I'm not quite sure it makes much sense to support that.

I understand your use case, but it seems fairly hacky to put that in the Makefile. I myself do something similar with Lilypond files, but have a separate (run) command to show the generated PDF, which doesn't have the problem you're facing.

from geany-plugins.