> It would be good if Geany could organize its sockets so that more than the > first open instance could be communicated with.
See --socket-file or -c [here](https://www.geany.org/manual/current/index.html#command-line-options) > Ideally, the most recently focused editor would accept document open > commands. Needs some system wide shared global thing that records who was the last Geany to be focussed, but I doubt it will be very useful on systems with "focus follows mouse" since it would be too easy to change which Geany that was. > What would be cool is if I could type open or edit instead, to open them in > the current instance. See above. You can define your own `open` or `edit` aliases since the terminal has a shell running inside it. (Note Geany does not see anything that you type in the terminal other than a few shortcut keys, it all goes directly to the shell) > We could tackle multiple-instance communication by allowing successive > instances to listen on the existing socket, or just having them create > sequential new sockets. I prefer the former. Unix sockets allow multiple listeners, but only one of them can read a message, so its the one taht wins the race that gets it. You need a shared server (the "global thing" referred to above) that communicates wit all the instances. IMO this is all becoming too complex just to automate which Geany gets an open request, its better to specify it explicitly as above. > I believe this change isn't all that complicated, and might be interested in > making it if the team doesn't have any other plans. Let me know. Other than the fundamental flaw noted above :) -- 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/issues/1727#issuecomment-353765250
