Windows path to unix path

Some user-space programs in Windows such as, oh, the Windows shell explorer. That's just shoddy programming in those programs. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Is it safe to convert Windows file paths to Unix file paths with a simple replace? Ask Question. Asked 7 years, 7 months ago. Active 1 year, 4 months ago. Viewed 33k times. Improve this question. Just watch out for spaces -- putting spaces in windows folder names is much more common than in unix directory names.

MxyL The problem doesn't go away when you hard-code the path instead of using an environment variable. If you just want a path that doesn't blow up, you should be fine. If you want a meaningful path, or if you want to interact with other software or user expectations The paths I am converting should be simple enough that they are meaningful by themselves. Backslashes are allowed in filenames on Linux, so replacing backslashes in a Linux path could add invalid directories.

Show 10 more comments. Active Oldest Votes. Sign in to answer this question. Unable to complete the action because of changes made to the page. Reload the page to see its updated state. Select a Web Site. Choose a web site to get translated content where available and see local events and offers. Based on your location, we recommend that you select:. Select the China site in Chinese or English for best site performance.

Other MathWorks country sites are not optimized for visits from your location. Toggle Main Navigation. Search Answers Clear Filters. Answers Support MathWorks. Search Support Clear Filters. Support Answers MathWorks. But if I had 2 files f1 and f2 , how would that work? I mean, how do I re-assign the new filenames to the array by replacing the old ones? WR put em in a new array and use that. WR Added that into the answer — wjandrea. I'd recommend to make a new array, for clarity's sake.

If it's something you want to do many times, then why not create a little shell function? That's not a bad idea. WR apologies - copy-paste error. Please try it now. Is this question still open to new suggestions? If so, would this help you? I must add that the other suggestions also work.

Many Unix command can do the same work, so its up to you what style of solution you prefer use. It's essentially a : -separated list of directories.

When you execute a command, the shell searches through each of these directories, one by one , until it finds a directory where the executable exists. Each one of these commands gets executed every time you create a new shell. If you wish to have certain directories automatically added to PATH , simply place those commands at the end of this file.