Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Make the current location for script blocks executing in background/thread jobs default to the caller's in all scenarios #10673
Ideally, we'd have a consistent experience across all background-/thread-job related features, meaning that all of the following should exhibit the same behavior with respect to the current location that the script block being passed sees (by default:
The most sensible location to use is the caller's current location, which (c) already uses and (d) will, once #10672 is merged.
The proposal is to make (a) and (b) behave like (c) and (d) for overall consistency and use of a sensible default:
The question now is:
Can we consider
I'm certainly personally in favor of that, but I haven't looked into how likely it is that existing
@PowerShell/powershell-committee discussed this, we agree that each of these should standardize on using the current working directory as the working directory.