Cygwin
-
vl2 wrote:
Just not the way windows-minded folk expects it to.
That is similar to claiming that OSX works on Macs but because it doesn't work on a windows machine that the windows machine is broken. And presumably you would also claim that Linux is broken since it provides methods that allow spaces in paths as well.
You're free to use spaces in paths, of course. Just never expect any scripts with string escaping work with them. No matter what your OS is. Something is terribly broken in the heads of those who allows spaces in the paths - they're making it nearly impossible to deal with their infrastructure with any scripting environment. COMMAND.COM chokes on spaces too, by the way.
-
Why is it "supposed to work", to start with? Windows mindset is such an amusing, funny little thing!
When in Rome .. well you know the saying. Having a limitation "installation directory may not contain spaces" is a bug. There are simply no excuses. Paths contains spaces on Windows. Almost always. That limitation essentially means it can't be installed at all, except in some places that are off-limits like "C:\". How would you like it if people "ported" things from windows to linux and kept all the windows-quirks?
-
You're free to use spaces in paths, of course. Just never expect any scripts with string escaping work with them. No matter what your OS is. Something is terribly broken in the heads of those who allows spaces in the paths - they're making it nearly impossible to deal with their infrastructure with any scripting environment. COMMAND.COM chokes on spaces too, by the way.
vl2 wrote:
COMMAND.COM chokes on spaces too, by the way.
Command.com? Perhaps you were referring to cmd.exe. I use spaces in paths in the batch scripts that I write for windows and nothing "chokes" so other than that I have no idea what you are referring to.
vl2 wrote:
they're making it nearly impossible to deal with their infrastructure with any scripting environment.
Actually rather trivial in my experience. At least once one is aware of it and handles it properly. Much harder for example, in my experience, to track down different types of syntax for different script languages.
-
Why is it "supposed to work", to start with? Windows mindset is such an amusing, funny little thing!
vl2 wrote:
Why is it "supposed to work", to start with?
You do in fact understand what OS Cygwin runs on right? You also understand that even when Cygwin was introduced the concept of dual booting already existed so if someone did in fact want to run Linux/unix then they had that option already. Thus the point of Cygwin is to add to the windows environment,not replace it - and you also understand that?
-
vl2 wrote:
Why is it "supposed to work", to start with?
You do in fact understand what OS Cygwin runs on right? You also understand that even when Cygwin was introduced the concept of dual booting already existed so if someone did in fact want to run Linux/unix then they had that option already. Thus the point of Cygwin is to add to the windows environment,not replace it - and you also understand that?
Point of Cygwin is to make Windows at least a little bit usable, because without the normal scripting tools it was just a shell for running Word (which is itself pretty useless too). Removing spaces from the "standard" paths is a tiny price for such a huge value.
-
vl2 wrote:
COMMAND.COM chokes on spaces too, by the way.
Command.com? Perhaps you were referring to cmd.exe. I use spaces in paths in the batch scripts that I write for windows and nothing "chokes" so other than that I have no idea what you are referring to.
vl2 wrote:
they're making it nearly impossible to deal with their infrastructure with any scripting environment.
Actually rather trivial in my experience. At least once one is aware of it and handles it properly. Much harder for example, in my experience, to track down different types of syntax for different script languages.
-
vl2 wrote:
Pass a path from one .bat script to anothe
I bet I would be lost in complexity in no time so paths have nothing to do with it. Script languages for OS shells are quick convenience only. For complex solutions I write applications in real languages.
-
Point of Cygwin is to make Windows at least a little bit usable, because without the normal scripting tools it was just a shell for running Word (which is itself pretty useless too). Removing spaces from the "standard" paths is a tiny price for such a huge value.
vl2 wrote:
Point of Cygwin is to make Windows at least a little bit usable
Nonsense.
vl2 wrote:
because without the normal scripting tools it was just a shell for running Word
Not sure what you are referring to but I was running scripts in windows before cygwin existed.
-
vl2 wrote:
Pass a path from one .bat script to anothe
I bet I would be lost in complexity in no time so paths have nothing to do with it. Script languages for OS shells are quick convenience only. For complex solutions I write applications in real languages.
-
vl2 wrote:
Point of Cygwin is to make Windows at least a little bit usable
Nonsense.
vl2 wrote:
because without the normal scripting tools it was just a shell for running Word
Not sure what you are referring to but I was running scripts in windows before cygwin existed.
-
Funny, how windows-minded people are struggling to comprehend such a simple thing as Unix Way. That's why automation is something nearly unheard of in the windows world.
vl2 wrote:
Funny, how windows-minded people are struggling to comprehend such a simple thing as Unix Way
There is no struggle for me given that I use both OSes and have delivered products intended to be run on both, sometimes the same product. But given that I do in fact deliver products and must deal with support issues I understand that the target is not my own preconceived biases but rather what the target OSes use and what customers expect.
vl2 wrote:
That's why automation is something nearly unheard of in the windows world.
Maybe in your world.
-
You just confessed that you do not understand scripting at all. How were you "running scripts" then?