[Bug] Issue with Cmder's first run when the PATH env variable contains double quotation (") character

[azraellamber]

Version Information

Cmder version: 1.3.25
Operating system: windows 10 22H2

Description of the Issue

When starting Cmder, an error message appears that says: "it should not be here..." followed by several system environment PATH variable entries. Additionally, the ls and pwd commands fail with an "error not found" message.

Upon further investigation, I found that one of the PATH environment variable entries contained a double-quoted string. After removing the double quotes from that entry, Cmder initialized correctly.

It seems this issue affects Cmder only during its initial setup. Once Cmder initializes successfully, it can start normally in subsequent runs, even if the PATH variable contains quoted entries.

Steps to Reproduce

1. Add a double-quoted string to one of the PATH entries in the environment variables.
2. Start Cmder for the first time on the computer.
3. Observe the error during initialization.

[DRSDavidSoft]

Thanks for the report ❤️

This is low priority to fix, because as the double quote symbol (") is part of forbidden characters both in the file name and path conventions of Windows, this is considered an invalid value to begin with.

Cmder can implement a feature to either: a) warn about the mis-configuration b) ignore the invalid path.

However, since there isn't any ideal way to process and parse the corrupted PATH env var, (and since I assume this doesn't affect that many users) I'm going to vote this as low priority.

Still, keeping it open to fix in a later time.