Skip to content

[Bug] cmder cannot init properly because the system env PATH with double quotation #2999

@azraellamber

Description

@azraellamber

Version Information

Cmder version: 1.3.25
Operating system: windows 10 22H2

Cmder Edition

Cmder Full (with Git)

Description of the issue

It prompt the messge "it should not be here..." at the cmder start line, and followed some system env PATH item strings.
then I found the commands ls and pwd with error not found.
So, I check the env PATH, found one of the env PATH item with the double quotation.
After removed that, cmder init correctly.
It may only has affect on the init works of cmder. After first init works correctly, cmder can start normally whether env PATH item with quotation.

How to reproduce

add quotation in one of the env PATH item before cmder init works at first start on computer

Additional context

No response

Checklist

  • I have read the documentation.
  • I have searched for similar issues and found none that describe my issue.
  • I have reproduced the issue on the latest version of Cmder.
  • I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions