Powershell breaks with semicolons in the PATH environment variable

[Windows 10]

I've been going down a rabbit hole with how Powershell processes the PATH environment variable. I am developing a program that helps manage the PATH, and I recently discovered that it has issues when a path containing semicolons is added to the PATH.According to [this comment on Github](https://github.com/HorridModz/Flow.Launcher.Plugin.Add2Path/pull/8#issuecomment-2596593503) by another user, Powershell interprets the PATH by splitting using the delimiter, which is a semicolon. However, it interprets quotes literally.This is a problem, because adding a folder path that contains a semicol

Continue reading...