I spoke too soon. I'm still seeing this problem but only under very peculiar circumstances in that it only happens if I launch geany from a Python script using:
subprocess.Popen(["geany", "-i"]) (also without the "-i") but (and here's the weird part) only if the Python code is being executed from within a GNOME Terminal or from within a program that was started from inside a GNOME Terminal. Just made another test and it also happens if I launch geany directly from the command line in a GNOME Terminal. (The version I have installed is GNOME TERMINAL 3.20.2 and it may not be the case for other versions.) If I start geany from the menu or using Python inside a program launched from the menu (or from a program launched from geany's terminal) I don't see the problem. So it seems that there's some sort of weird interaction between geany and GNOME Terminal but I'm not sure if it's worth pursuing this issue any further. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-osx/issues/3#issuecomment-251567959
