Feature Request: Create a preference variable to turn Off/On path normalization #3118

Activity

1. Richard Burte (arebee)

   changed the title [-]Create a preference variable to turn Off/On path normalization[/-] [+]Feature Request: Create a preference variable to turn Off/On path normalization[/+] on Feb 9, 2017
2. thezim commented on Feb 9, 2017

   

   Greg Zimmerman (thezim)

   on Feb 9, 2017

   Contributor

   More actions

   I had an similar issue today where I used Split-Path on a URL stem on Windows and it autocorrected the path delimiter. Would be nice if there was a switch for this particular cmdlet to ignore translation.

   PS C:\> Split-Path -Parent -Path /one/two
   \one

   👍React with 👍1Reacted by Michael Klement
3. iSazonov commented on Feb 10, 2017

   

   Ilya (iSazonov)

   on Feb 10, 2017

   Last edited by joeyaiello

   Collaborator

   More actions

   We should have both:

   1. Global preference variable with default value a platform depended.
   2. Switch -Normalize or parameter -Style [Windows | Unix]
      What cmdlets is affected by the issue?
4. thezim commented on Feb 11, 2017

   

   Greg Zimmerman (thezim)

   on Feb 11, 2017

   Contributor

   More actions

   Ilya (@iSazonov) -Style [Windows | Unix] make more sense from a discovery point of view. Also -Normalize could get confusing if you have preferenced something else already, better to avoid the ambiguity.
5. Joey Aiello (joeyaiello)

   added

   WG-Interactive-IntelliSensetab completiontab completion

   on Feb 11, 2017
6. iSazonov commented on Feb 12, 2017

   

   Ilya (iSazonov)

   on Feb 12, 2017

   Last edited by iSazonov

   Collaborator

   More actions

   We should have switches (in different parameter sets):
   -StyleWindows - default true on Windows
   -StyleUnix - default true on Linux and IOS.

   And we should consider remoting and remote sessions Windows -> Unix, Unix -> Windows. Is it possible and reasonable to make implicit conversions?
7. arebee commented on Feb 12, 2017

   

   Richard Burte (arebee)

   on Feb 12, 2017 via email

   Author

   More actions

   -PathDelimiter [Windows|Unix] $PSPathDelimier = [Windows|Unix] defaults to platform. This should be a cosmetic styling.

   …

   Sent from my Windows 10 phone From: Ilya Sent: Sunday, February 12, 2017 4:40 To: PowerShell/PowerShell Cc: Richard Burte; Author Subject: Re: [PowerShell/PowerShell] Feature Request: Create a preferencevariable to turn Off/On path normalization (#3118) We should have switches (in different parameter sets): -StyleWindows - default true on Windows -StyleUnix - default on Linux and IOS. And we should consider remoting and remote sessions Windows -> Unix, Unix -> Windows. Is it possible and reasonable to make implicit conversions? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
8. Steve Lee (SteveL-MSFT)

   added

   Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bug

   on Mar 5, 2017
9. Steve Lee (SteveL-MSFT)

   added this to the 6.1.0This milestone has been deleted milestone on Mar 5, 2017
10. Steve Lee (SteveL-MSFT)

    modified the milestones: 6.1.0-Consider, 6.2.0-Consider, Future on Jun 15, 2018
11. microsoft-github-policy-service commented on Nov 16, 2023

    

    microsoft-github-policy-serviceBot

    on Nov 16, 2023 – with Microsoft GitHub Policy Service

    Contributor

    More actions

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
12. microsoft-github-policy-service commented on Nov 16, 2023

    

    microsoft-github-policy-serviceBot

    on Nov 16, 2023 – with Microsoft GitHub Policy Service

    Contributor

    More actions

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
13. microsoft-github-policy-service

    added

    Resolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more

    on Nov 16, 2023
14. microsoft-github-policy-service commented on Nov 16, 2023

    

    microsoft-github-policy-serviceBot

    on Nov 16, 2023 – with Microsoft GitHub Policy Service

    Contributor

    More actions

    This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
15. microsoft-github-policy-service commented on Nov 23, 2023

    

    microsoft-github-policy-serviceBot

    on Nov 23, 2023 – with Microsoft GitHub Policy Service

    Contributor

    More actions

    This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.
16. microsoft-github-policy-service

    removed this from the Future milestone on Nov 23, 2023
17. microsoft-github-policy-service

    closed this as completedon Nov 23, 2023