Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on How to convert Dos paths to Posix paths in Powershell

Post

How to convert Dos paths to Posix paths in Powershell

+3
−0

What is the best way to convert Dos paths to Posix paths in Powershell? eg given:

C:\Program Files\PowerShell\Modules\

I want something like:

/Program\ Files/PowerShell/Modules/

Is the only solution to escape spaces and convert backslashes?

I've searched the web but couldn't find any existing Powershell function, and the solutions I found didn't mention escaping spaces, so I don't hold much hope that they're complete.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

What is your goal? (1 comment)
Do you need to escape the spaces? (3 comments)
Do you need to escape the spaces?
H_H‭ wrote 9 months ago · edited 9 months ago

Posix accepts any character (means any byte value) in filenames except '/' and NULL. The escaping of spaces are only needed for things like shell scripts, so the shell doesn't split the path at the ' '.

AFAIK winepath from the Wine project, also doesn't escape spaces when converting a Windows path to a Unix path.

If you need to escape them, you may have to specify how a Posix path should look like.

The thing that makes the conversation hard is that there is no way to map 1:1. In windows you have different letters for partitions, which letter is mounted where in the / structure?

kjw‭ wrote 9 months ago · edited 9 months ago

Ah, I didn't understand that it was the shell that needed the escaping.

And yeah, found that mapping problem too - which I can work around locally.

So that means escaping or swapping the '/' is the only thing that needs to be done.

This is the answer I'm after, thanks!

H_H‭ wrote 8 months ago

Well, there are special filenames in Windows such as CON, COM, and NUL. If you have such a filename you need a bit more logic to convert them. For example CON2 would be something like /dev/ttyS1, /dev/ttyUSB0, /dev/ttyAMA0 .... You probably shouldn't use this filenames anyway.