oh-my-posh: Unable to change theme since v3.75.1
Prerequisites
- I have read and understand the
CONTRIBUTINGguide - I looked for duplicate issues before submitting this one
Description
After upgrading to the latest version of the PowerShell module I noticed that the theme was reset to the default one. I tried to change it but the command Set-PoshPrompt -Theme sorin does not work. So I started downgrading and with v3.75.0 it started working again.
This is my PowerShell profile:
Import-Module oh-my-posh
Set-PoshPrompt -Theme sorin
Environment
- Oh my Posh version: 3.75.1 / 3.75.2 (both broken)
- Theme: sorin
- Operating System: Windows 10 19042.746
- Shell: PowerShell Core 7.1.1
- Terminal: Windows Terminal Preview 1.5.3242.0
Steps to Reproduce
- Install v3.75.1
- Import module and try to change change theme
Expected behavior: The prompt should change to the selected theme.
Actual behavior: The prompt does not change.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 18 (13 by maintainers)
Commits related to this issue
- fix(pwsh): encode config path resolves #355 — committed to JanDeDobbeleer/oh-my-posh by JanDeDobbeleer 3 years ago
- fix(pwsh): provide full config path resolves #355 — committed to JanDeDobbeleer/oh-my-posh by JanDeDobbeleer 3 years ago
@rolflobker someone added a
\bin there which is a backspace character and fails to get parsed properly after export. I removed them we’ll see what breaks when an issue pops up 😉I will allow that.
I am able to copy the file to C: and set the theme now. Thanks.
On the other note,
~/Documents, where Powershell’s modules get installed on this PC is on a network drive, with the path containing a$. I’m not sure if that’s a problem.Do you know what was causing the problem? I also find it weird it says UNABLE TO OPEN CONFIG. I’m getting this with version 3.129.0
Just upgraded and the issue is gone. 👍 Thank you a lot for the quick fix and your dedication to this awesome tool.