Geany 1.37 does different behaviour for me on macOS. If I invoke it with no file argument then it opens a brand new Geany process and Window. However, if I invoke it with a file argument then it will open the file in the original Geany process window. This behaviour is a little unusual :-)

Yes, when you run Geany from the command line (without specifying any files to open), it creates a new instance (and yes, this is not quite a native behavior). I'm just trying to understand if this is some problem that makes Geany harder to use in some situations - clearly, if this happened for opening new files from the command-line, this would be annoying, but does one actually run geany without any files when another instance of Geany is already running?

This is in principle possible to fix by introducing one more command-line paramter to Geany to always reuse existing instance, I'm just trying to understand whether it's something worth doing (on linux running geany from the command lines without any files as arguments always creates a new instance so this functionality is missing in Geany itself).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.