Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Good guess.
I tested this and Windows Explorer in fact spawns a single Geany process per selected file and then this happens what @elextr described above.
There is probably no easy solution. Making the initial startup faster until the socket connection is checked or implementing some other kind of early locking could make it better but there might be still systems or situations where the startup of the first process is slow enough than the second does not yet see the first one.
Maybe Windows Explorer can be told to start one only process and pass all files to it but I don't know whether this is possible.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.