Re:Windows 10: The Next Chapter [video]
by loarabia on Wednesday January 21, 2015 @08:16PM
(#8926923)
Good feedback. When you work in Cygwin, are you doing admin type tasks, web dev, writing console utilities, something else related to app dev?
Re:Windows 10: The Next Chapter [video]
by diminoten on Thursday January 22, 2015 @03:51PM
(#8931665)
In systems where I find myself in the shell, I tend to prefer the shell to everything except certain system configuration tasks (I like the shell for things like tweaking network settings, but dislike it for things like printer config, for example), and for actual software dev (IDEs still win for me).
Once I feel I can buy into the shell, I'll probably go all in. Until then, I try to use Cygwin to avoid having to switch to a *nix box when I just want to use a simple admin utility or maybe test something out in the Python REPL, but otherwise I just tend to switch when I want to spend a work day on something.
Re:Windows 10: The Next Chapter [video]
by elektronjunge on Wednesday January 21, 2015 @02:18PM
(#8924974)
You can use forward slashes in paths in cmd and powershell. But yes, I agree with your main point.
I don't want to have to relearn commands that I know work in *nix land, is the big point -- I don't want to have to remember to change the directions of my slashes, for example.
I'm not an expert, merely a user, in this space, so I can't really articulate precisely what it is I want in the best terms possible, but I can say I get a lot closer to where I want to be with Cygwin than I get with anything that comes native on Windows.