Skip to main content
24 events
when toggle format what by license comment
Apr 18, 2021 at 1:39 audit First posts
Apr 18, 2021 at 4:37
Apr 12, 2021 at 16:49 comment added Dev @SebastiaanvandenBroek The comment I replied to stated that Linux also had the same faulty third-party programs. That's what I was addressing.
Apr 12, 2021 at 12:26 history edited Run5k CC BY-SA 4.0
Minor grammar fix
Apr 12, 2021 at 10:11 comment added Kamil Maciorowski Feedback: I like the other answer because it touches what your answer misses: a hypothetical command videoplayer.exe /video C:\Games\Half Life\intro.avi "fixed" by quoting like this: videoplayer.exe /video "C:\Games\Half Life\intro.avi" may or may not succeed; it depends on whether or not videoplayer.exe supports quoting. There is a bug in the game but it's not necessarily because "the code opens video without quotes". Maybe videoplayer.exe is crippled in the first place.
Apr 12, 2021 at 7:11 comment added Peter - Reinstate Monica @Dev Passing all arguments in a single string is not a bug but a design flaw, creating generations of headaches for developers: "CommandLineToArgvW treats whitespace outside of quotation marks as argument delimiters." Uh-hm. Vs. "On *nix, the parameters are parsed off by whatever program creates the new process." No formatting or parsing headaches whatsoever (except for a user shell).
Apr 12, 2021 at 7:01 comment added Peter - Reinstate Monica @Aganju Actually, whoever had the idea to allow spaces in paths should be flogged and quartered. That was probably a costlier mistake than the nullpointer.
Apr 12, 2021 at 6:45 comment added LPChip @KamilMaciorowski The Half Live is a typo on my end... well spotted. Fixed. :) When calling programs without quotes, windows often still works, but it may also break, so that's a valid point.
Apr 12, 2021 at 6:43 history edited LPChip CC BY-SA 4.0
edited body
Apr 12, 2021 at 6:22 comment added Sebastiaan van den Broek @Dev context is important. See what you replied to and what they replied to.
Apr 12, 2021 at 6:21 comment added Dev @SebastiaanvandenBroek Nowhere did I say this was a Windows problem, thank you. It's just a general trend with old Windows programs, not the fault of the OS, unless encouraging bad coding practices counts. :)
Apr 12, 2021 at 5:32 comment added Kamil Maciorowski (1) Why HalfLife and HalfLive? (Occam's razor: entities should not be multiplied without necessity). (2) There is a space in C:\Games\Half Life\bin\videoplayer.exe. The answer suggests the string is somehow interpreted as one entity despite the lack of quoting; at the same time C:\Games\Half Live\intro.avi is two entities because of lack of quoting. (3) videoplayer.exe may not support quotes at all (compare this).
Apr 12, 2021 at 4:19 comment added phuclv @Aganju not quoting paths with spaces properly is a bug of the program and has nothing to do with Windows. Any apps that don't work with spaces in file names are shitty these days
Apr 12, 2021 at 2:13 comment added Sebastiaan van den Broek @Dev that still doesn’t mean it’s Windows being buggy though. Although it is quite possible that more developers for the Windows platform would make a mistake like this, simply because they’re not as used to working with the command line. Not because they’re not as good (I wouldn’t call game developers poor programmers) but because they don’t need that knowledge as often.
Apr 12, 2021 at 1:39 comment added Dev @ToddSewell it's more prevalent in old Windows programs that use composition via routing arbitrary strings through COMMAND.COM or CMD.EXE. Even in the olden days of Linux, people knew to use quotation marks in their shell scripts, and programs that executed subprocesses often passed argv as an array of strings anyway, so they didn't have to deal with escaping arguments for a shell.
Apr 12, 2021 at 0:03 comment added KarelPeeters @Aganju not in windows, in 3rd party programs. Linux has the same exact "issue".
Apr 11, 2021 at 22:36 comment added Aganju In other words, lots of Windows is still buggy, after 30 years of improvement. Hardly a surprise, though.
Apr 11, 2021 at 22:31 comment added David Schwartz Lots of Windows stuff fails in strange ways if your user name has a space in it. :(
Apr 11, 2021 at 22:17 comment added hanshenrik @Vikas to see the problem for yourself, run this in cmd as administrator: mkdir "C:\foo" \n mkdir "C:\foo bar" \n copy "%windir%\system32\timeout.exe" "C:\foo" /y \n copy "%windir%\system32\timeout.exe" "C:\foo bar" /y \n C:\foo\timeout.exe 5 \n C:\foo bar\timeout.exe 8 \n (just replace the \n with enter)
Apr 11, 2021 at 18:37 comment added LPChip Done. Hope this helps.
Apr 11, 2021 at 18:37 history edited LPChip CC BY-SA 4.0
added 1234 characters in body
Apr 11, 2021 at 13:30 comment added Vikas What I'm thinking is: var path_name = sdfdf/sdfdf/FolderName works while var path_name = sdfdf/sdfdf/Folder Name; will give error because there's unwanted space?
Apr 11, 2021 at 13:26 comment added Vikas If possible would you please also add a bit more explanation of how that "code error" would work? I have done coding in past so I'll probably understand.
Apr 11, 2021 at 13:25 vote accept Vikas
Apr 11, 2021 at 13:24 history answered LPChip CC BY-SA 4.0