News for hackers. Stuff that matters.

A comment on Microsoft Adds an OpenSSH Client to Windows 10. Parent comment

Re:Microsoft Adds an OpenSSH Client to Windows 10 by cjsuk on Tuesday December 12, 2017 @07:15AM (#15905020)
The big problem is the filesystem is still vastly different.

The web, Unix, Linux, OSX, pretty much everything other than Microsoft uses properly namespace driven forward-slash separated paths with no drives and case sensitivity.

That you can't fix, merely abstract it away. I am tired of mapping between the two.

   scp myfile.txt winmachine:/d/Users/Whoever/Documents/Projects/X/File.txt
Then I cut and paste. Oh no wait I can't. Now I have to replace all the /'s with \'s and d with d:...

Or

   scp myfile.txt linmachine:/home/whoever/documents/projects/x/file.txt
I'm done and moved over the fence. \ means escape. / means path separator. No \\ problems either.
[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by nailer on Tuesday December 12, 2017 @07:21AM (#15905059)
Totally agreed, I always use slash, and never use backslash, because I'm a 20 year nix user, and: powershell doesn't care. try it.
[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by cjsuk on Tuesday December 12, 2017 @08:08AM (#15905312)
Powershell doesn't but not everything is powershell. Win32 underneath pokes its head out occasionally. And I don't want to use powershell. It's horrid in so many ways.

I'm a Unix user since about '93 for ref as well. I am poisoned with forward slashes everywhere :)

[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by coldacid on Tuesday December 12, 2017 @08:51AM (#15905541)
MS-DOS (and Windows) have supported forward slashes as path separators since PC-DOS 2.0, despite defaulting to backslash. Anywhere where the forward slash isn't supported is a bug either in Windows or (more likely) in the app that won't accept them.
[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by arundelo on Tuesday December 12, 2017 @10:16AM (#15906106)
I use forward slashes a lot on Windows but tab completion in cmd.exe only works with backslashes.
[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by coldacid on Tuesday December 12, 2017 @09:05PM (#15911421)
Yeah, that's a shortcoming with cmd.exe. At least PowerShell will switch slashes to whichever is default for the platform, but I doubt that supporting fore-slash tab completion in cmd.exe would be able to crawl out of the -100pt hole.
[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by nailer on Tuesday December 12, 2017 @08:34AM (#15905440)
That makes sense: I don't do anything on Windows command line that isn't powershell. Give it a chance: install PSCX, openssh, and conemu, configure your emacs keybindings, steal my profile (https://github.com/mikemaccana/powershell-profile) and learn, at minimum, 'where', 'get-member' and 'select' before you make your mind up on anything.
[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by AnIdiotOnTheNet on Tuesday December 12, 2017 @11:58AM (#15907105)
> And I don't want to use powershell. It's horrid in so many ways.

Name one that isn't just "Bourne Shell does it different".

[ Parent | on HN ]
Re:Microsoft Adds an OpenSSH Client to Windows 10 by kccqzy on Tuesday December 12, 2017 @05:45PM (#15910184)
OS X’s filesystem isn’t case sensitive by default.
[ Parent | on HN ]