Skip to content
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.

Sign up for GitHub

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

Jump to bottom

当我向wsl子系统命令行中粘贴路径的时候无法自动转换 #5011

Closed
mo7cc opened this issue Mar 19, 2020 · 7 comments
Closed

当我向wsl子系统命令行中粘贴路径的时候无法自动转换 #5011

mo7cc opened this issue Mar 19, 2020 · 7 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mo7cc
Copy link

mo7cc commented Mar 19, 2020

cmder中:
图片

windows terminal 中:

图片
@mo7cc mo7cc added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 19, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Mar 19, 2020
@mo7cc
Copy link
Author

mo7cc commented Mar 19, 2020

图片

@mo7cc
Copy link
Author

mo7cc commented Mar 19, 2020

比如git-bash 命令 , 在 windows terminal 中也是无法做到正确转换的

@skyline75489
Copy link
Collaborator

To my understanding, this is about different behaviours between cmder and Windows Terminal when it comes to copy&pasting file URL.

I think it's a nice feature, to automatically convert C:\ to /mnt/c. I do not use cmder so I'm not aware of this feature in cmder.

@j4james
Copy link
Collaborator

j4james commented Mar 19, 2020

If it's about path translation, then this is probably duplicate of #1772.

@mo7cc
Copy link
Author

mo7cc commented Mar 19, 2020

If it's about path translation, then this is probably duplicate of #1772.

yes

@zadjii-msft
Copy link
Member

Thanks for the help triaging everyone!

/dup #1772

@ghost
Copy link

ghost commented Mar 19, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Mar 19, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 19, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@j4james @skyline75489 @zadjii-msft @mo7cc