Thank you for the quick reply.
It looks like it may be sitting and waiting when I open a console from a build command button I made - sometimes. (I think I made it happen once a moment ago.)
I typically start an edit session with a script that opens from 4 to 6 geany projects on different screens, with up to 3 other terminals/file managers open on a single desktop with geany. So ... minimum 4 geany sessions with 50+ (remote) files total + 7 consoles + 2 file managers with one script.
Rarely have a problem. Some of my edit profiles are much larger.
My console command ( is:
[build-menu]
NF_03_LB=console
NF_03_CM=lxterminal --geometry=130x30& --working-directory=%d
NF_03_WD=
Can something be used or option set, like a '&' in a script, to have geany NOT wait for a response?