New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
broot --install on Windows PowerShell updates the wrong Profile.ps1 file #806
Comments
I'd like rusticians with knowledge of Windows to have a look there. |
But So imo what broot does here is correct, and the best option as well. |
Unfortunately no, I had to manually source the broot ps1 script in my |
Right, I missed that you're probably running PS Core, hence it looks in Anyway, the typical fix for this PS/PS Core discrepancy is symlinking the WindowsPowershell to the Powershell directory or vice-versa. |
I think we should be revisiting this; the install script is currently in a broken state anyway* and we need to get eyes on it. *: Last I checked, needs to be installed twice before br works, and then br will have you install it a third time 🤪 Note: PScore is typically referred to as pwsh, while the version currently bundled with Windows is referred to as WindowsPowerShell. This will be the familiar nomenclature to anyone who opted to install pwsh. I propose the following change:
By the by, If ((Get-Host).version.major -gt 5) {
// this won't run in powershell 5
} |
A focused PR not touching other systems could be welcome here. |
Encountered exactly this issue today. |
>> broot --version
>> broot 1.30.0
>> broot --install
However, my Profile file is different:
>> echo $PROFILE
>> C:\Users\arusev\OneDrive - XXX\Documents\PowerShell\Microsoft.PowerShell_profile.ps1
The text was updated successfully, but these errors were encountered: