@codebrainz I reproduced the child command window issue on a relatively fresh
window 10 VM, so I don't think its anything exotic about my machine.
Steps to reproduce:
launch a fresh copy of geany. Default settings are fine
Execute a script such as this. I used python, but I don't think the language is
important
```import time
while True:
print "foo"
time.sleep(5)
```
The idea is, you want something that continually executes.
Now, while the script is "foo"ing, close geany. The command window will stay
open, and it will keep printing foo.
Double click any text file from windows explorer (or right click open with
geany, etc). Geany will launch your file
Double click another text file from windows explorer. Geany will launch a
second concurrent instance. 3rd, 4th, 5th, files will all load in their own
instance
Now to resolve it: close all geany instances, then close the "foo" script
window.
Now open a file with geany, then a 2nd, 3rd, 4th file from windows explorer,
all will open in the same geany instance as expected.
Unless, of course, you meant the crashing issue? I'm not exactly "a windows
guy", I'm "a linux guy" stuck on windows for my job but I think I managed to
install gdb for windows, and I currently have geany running in gdb.exe, running
in powershell. I'll leave it like that for a few days and see if I can capture
a stacktrace from a crash. That issue is intermittent tho, so no guarantee on
when I get it
--
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/2555#issuecomment-672877493
