-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Set-Location -Path + fails because it mishandles the history #14279
Copy link
Copy link
Closed
Labels
Area-FileSystem-Providerspecific to the FileSystem providerspecific to the FileSystem providerIssue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Cmdlets-Managementcmdlets in the Microsoft.PowerShell.Management modulecmdlets in the Microsoft.PowerShell.Management module
Metadata
Metadata
Assignees
Labels
Area-FileSystem-Providerspecific to the FileSystem providerspecific to the FileSystem providerIssue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Cmdlets-Managementcmdlets in the Microsoft.PowerShell.Management modulecmdlets in the Microsoft.PowerShell.Management module
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce
Open a PowerShell 7.1 window, navigate to a safe folder for experimentation, and issue the following commands:
Expected behavior
After following the reproduction steps, the user expects the current folder to be the '[Meta]' folder.
Actual behavior
In PowerShell 7.1, I received the following error:
Environment data