I thought about twiddling the environment inside my programs as you suggest but discounted it after I discovered that I got the same problem with geany's terminal if I launched geany directly from the command line inside the GNOME Terminal as this indicated that Python probably (if not definitely) wasn't implicated.
I'm going to avoid the problem by not using GNOME Terminal anymore. I mainly only use it when I'm testing my GUIs and need to be able to see any gumph that Gtk spits out to standard error or Python exceptions that I've failed to catch. Even though it might be wasteful of resources using geany for just its terminal I can use the terminal of a geany instance to achieve this end. I also might write a 20 (or so, excluding the GPL copyright notice) Python/PyGObject script that would provide a program with the essential functionality of GNOME Terminal without all the frills. -- 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-251577687
