Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
I don't know how Windows does it, but the same problem would happen if the default working directory is the one containing the file to open (e.g. if the WD is C:\A\B when opening file C:\A\B\c), which wouldn't seem particularly silly to me.
IIUC thats what the SF bug is about, windows locks its WD1, and so the only "solution" is to change the WD so windows locks some irrelevant directory. Because that directory has to exist to CWD to it, the Geany solution of using its install is reasonable, its pretty sure to exist :-).
Alternatively if Windowsers agree, we possibly could try and default the open/save dialogs to g_get_home_dir() on Windows I guess.
Thats possibly sensible, yeah.
its not as silly as it seems, not allowing the base for relative paths to be removed while the process executes is good. ↩
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.