News for hackers. Stuff that matters.
Re:Kinda like apt-get, but for Windows by pjmlp on Wednesday February 06, 2013 @08:42AM (#5176247)
I never understood what is so hard in treating the space as just another character.
Re:Kinda like apt-get, but for Windows by j-kidd on Wednesday February 06, 2013 @08:46AM (#5176260)
Because space is not just another character. Space separates args.
Re:Kinda like apt-get, but for Windows by ygra on Wednesday February 06, 2013 @09:51AM (#5176604)
But an installer talking to the operating system shouldn't need to separate arguments anywhere.
Re:Kinda like apt-get, but for Windows by laumars on Wednesday February 06, 2013 @10:18AM (#5176751)
Which is why escape characters and quotations were invented
Re:Kinda like apt-get, but for Windows by jfb on Wednesday February 06, 2013 @12:07PM (#5177522)
It is an abject failing of software that perfectly reasonable characters are barred from filenames.
Re:Kinda like apt-get, but for Windows by pjmlp on Wednesday February 06, 2013 @11:04AM (#5177035)
which is why most arguments tend to have a way to be recognized like -, -- or /
Re:Kinda like apt-get, but for Windows by lotyrin on Wednesday February 06, 2013 @03:06PM (#5178478)
Those are how one differentiates flags from arguments, which is a separate problem.
Re:Kinda like apt-get, but for Windows by pjmlp on Thursday February 07, 2013 @01:29AM (#5180865)
Kind of.

If your flag is for a path, you can assume everything up to the next flag is a path name.

myprog -filename here is my path with spaces -another_flag

Of course this depends on how the shell gives the arguments to the program.

On the other hand, there is no excuse why some GUI programs cannot handle spaces.

Re:Kinda like apt-get, but for Windows by lotyrin on Thursday February 07, 2013 @04:47PM (#5184714)
cp path1 path2

So, that's just one file?

Re:Kinda like apt-get, but for Windows by SideburnsOfDoom on Wednesday February 06, 2013 @10:33AM (#5176833)
Treating the space as just another character in a path means that sometimes paths have to be placed inside quotes so the space isn't taken for the end of a commandline arg. Some old software didn't do that.
Re:Kinda like apt-get, but for Windows by Nilzor on Wednesday February 06, 2013 @11:16AM (#5177116)
Chocolatey is not old software
Re:Kinda like apt-get, but for Windows by SideburnsOfDoom on Wednesday February 06, 2013 @11:36AM (#5177300)
No, it does not have that excuse.
Re:Kinda like apt-get, but for Windows by darkchasma on Wednesday February 06, 2013 @01:45PM (#5178048)
But the packages it installs may.
Re:Kinda like apt-get, but for Windows by negativity on Wednesday February 06, 2013 @12:53PM (#5177773)
The tilde file names in windows harken back to ye olde days of MSDOS, where file names were only allowed to be 8 characters long, and the extension was only allowed to be a dot followed by three characters (aka: the "eight-dot-three" file naming convention).

Like, if someone generated several thousand files, all named: "New Text Document.txt"

In the background, some versions of Windows will also record an alternate file name for ye olde backwards compatibility, such as:

NEWTEX~1.TXT

NEWTE~10.TXT

NEWT~100.TXT

NEW~1000.TXT

NE~10000.TXT

N~100000.TXT

It's not really about the space characters, so much as it is about length constraints from back when 640KB should've been more memory than anyone will ever need.