-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Getting error on importing the terminal icons module #121
Comments
If you don't mind 1 second delay below profile works for me with a 2x2 split terminal startup with pwsh 7.4.5
|
That looks like a very ugly workaround. 😅 Over time I figured out the source of the bug. It happens every time a new Powershell version is installed. What I didn't figure out is, what happens exactly that corrupts the xml file. My, slightly less ugly, workaround is to just delete the folder created by terminal-Icons and then let it recreate it. Since I don't use any modifications to the config, it doesn't matter to me. |
Unfortunately this isn't the case for me but the ugly workaround works ;) |
Expected Behavior
I can import the module using
Import-Module Terminal-Icons
without any issue.Current Behavior
Getting the error message when trying to import.
Import-Clixml: 'Element' is an invalid XmlNodeType. Line 210, position 22.
Possible Solution
As a workaround to fix it, just delete the
devblackops_*.xml
files, and then importing the module will create them again.Steps to Reproduce (for bugs)
Import-Module Terminal-Icons
Context
I'm getting this error message sometimes, but haven't figured out the root cause yet. I have an assumption that it is only happening when I update my PowerShell version.
The error refers to the
devblackops_icon.xml
file and the following piece of content:For some reason the closing tag
</En>
is broken in the file. But I have no idea what changed it, because it was working before.After using the workaround described above, I realized that the file was corrupted beyond just that missing closing tag. Unfortunately, I didn't make a copy before deleting it, so I can't attach it here. I will do that the next time the issue happens in the hopes this makes it easier to debug the issue.
Your Environment
The text was updated successfully, but these errors were encountered: