BUG: Explorer Plugin setting working directory seems to have not effect

[guntern]

Checks

• I have checked that this issue has not already been reported.

Problem Description

I am trying to start a python script directly via FlowLauncher. This worked fine with version 1.10 and the everything plugin. But with the new Explorer plugin I run into issues. I added debug output to my python script. And this revealed that it is started with C:\Windows\system32 as current working directory regardless of whether the corresponding checkbox in the explorer plugin is checked or not.
Is there anything I am missing in the configuration of the Explorer plugin to be able to run my python script directly from FlowLauncher again?
The script launches perfectly fine, when double clicked in Windows Explorer or when invoked via Powershell in its working directory.
The directory containing the script is not in PATH.

To Reproduce

1. Type name of python script in FlowLauncher
2. Hit Enter to run
3. Script reports that it is started with the wrong working directory

Screenshots

No response

Flow Launcher Version

v1.11.0

Windows Build Number

10.0.19045.2364

Error Log

Replace this line with the important log contents.

[deefrawley]

Hi,
In the settings for the Explorer plugin have you enabled the 'Use search result's l;ocation as the working directory of the executable' under 'General Setting'?

[guntern]

Yes I did. I checked with this option enabled and disabled and the python script reported the same working directory in both cases.

[jjw24]

I am trying to start a python script directly via FlowLauncher

How are you running this, just clicking on the result after searching with Explorer?

Do you have the shebang line in the script? If not I'd imagine you need to put python in front of it file, in this case how are you configure it to launch?

[taooceros]

Yes I did. I checked with this option enabled and disabled and the python script reported the same working directory in both cases.

I just take a look on that setting....and you are right, that's a setting with no effect.

[guntern]

I am trying to start a python script directly via FlowLauncher

How are you running this, just clicking on the result after searching with Explorer?

Do you have the shebang line in the script? If not I'd imagine you need to put python in front of it file, in this case how are you configure it to launch?

I just type part of the file name of the script until it turns up in the search results. Then I just hit Enter. Via the Everything plugin this worked, but not with the new one. Shebang is also included.

Apparently there was an issue with the setting. I am eagerly waiting for the change to end up in my version :-) Hopefully everything is resolved then. Thank you for now in either case.

[VictoriousRaptor]

You can try the prerelease of the PR (https://github.com/Flow-Launcher/Prereleases/releases/tag/v1.11.0.6815). It should fix this issue. Feel free to reopen this issue if it's still not working.

[guntern]

Thank you for the hint. I installed it, but it still reports itself as 1.11.0. How can I ensure that I am actually using this prerelease?
Unfortunately, I cannot ensure it by a working solution. I still have the same issue. But before blaming the solution I doubt my installation process.

By the way here my test python script:

#!python3
import os
import time

print("Flow Launcher Test")
print(os.getcwd())
time.sleep(5)

[VictoriousRaptor]

#!python3
import os
import time

print("Flow Launcher Test")
print(os.getcwd())
time.sleep(5)

Please try to exit flow and install the preview.

[guntern]

I tried that already the first time, but tried it again. I even checked in the task manager that flow is not running anymore.

For the first attempt I also got a warning, whether I trust the program and really want to install.

Now the second time nothing showed, when running the setup.exe. FlowLauncher was just running afterwards. I will give it a nother try this evening, with a bit more time.

[taooceros]

I will check again. I didn't really test the solution since it seems pretty straightforward.

[VictoriousRaptor]

Flow.Launcher/Plugins/Flow.Launcher.Plugin.Explorer/Search/ResultManager.cs

Lines 239 to 258 in c136022

	if (File.Exists(filePath) && c.SpecialKeyState.CtrlPressed && c.SpecialKeyState.ShiftPressed)
	{
	_ = Task.Run(() =>
	{
	try
	{
	Process.Start(new ProcessStartInfo
	{
	FileName = filePath,
	UseShellExecute = true,
	WorkingDirectory = Settings.UseLocationAsWorkingDir ? Path.GetDirectoryName(filePath) : string.Empty,
	Verb = "runas",
	});
	}
	catch (Exception e)
	{
	MessageBox.Show(e.Message, "Could not start " + filePath);
	}
	});
	}

The fix in #1788 is only used when Ctrl + Shift + Enter is pressed. But because it runs as admin, cmd's working dir is still set to system32.