Re:Kinda like apt-get, but for Windows
by j-kidd on Wednesday February 06, 2013 @08:42AM
(#5176249)
From their FAQ, it says that chocolatey is "CLI focused". So, "C:\chocolatey" makes sense. Paths with space are definitely less CLI-friendly than those without.
[ Parent
| on HN ]
Re:Kinda like apt-get, but for Windows
by SideburnsOfDoom on Wednesday February 06, 2013 @09:04AM
(#5176358)
Does install location matter to the CLI? The install location will be on path, so it will be usable from anywhere.
Well rather, if you want to muck about in the installation folder, typing "C:\choc<TAB>" is easier than "C:\Progr<TAB>\choc<TAB>"
Show me a CLI that doesn't auto-complete paths with spaces. I don't remember when I last had to type “Program Files (x86)” out in full.
Re:Kinda like apt-get, but for Windows
by niggler on Wednesday February 06, 2013 @01:29PM
(#5177961)
When you write CLI apps in .NET, for example, handling paths with spaces is a mess (argv splits on " ", even if you wrap arguments in quotes, so "C:\Program Files (x86)" is seen as 3 tokens.
Re:Kinda like apt-get, but for Windows
by ajanuary on Wednesday February 06, 2013 @02:04PM
(#5178153)
Really?
C:\Users\andrewj\Desktop>type test.cs
public static class Test {
public static void Main(string[] args) {
foreach (string arg in args) {
System.Console.WriteLine(arg);
}
}
}
C:\Users\andrewj\Desktop>csc test.cs
C:\Users\andrewj\Desktop>test.exe a b "C:\Program Files (x86)" d e
a
b
C:\Program Files (x86)
d
e
Do you mean "language x" on .NET?