4 ms·
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.
by j-kidd 14y ago
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.
- SideburnsOfDoom 14y agoDoes install location matter to the CLI? The install location will be on path, so it will be usable from anywhere.
- gcr 14y agoWell rather, if you want to muck about in the installation folder, typing "C:\choc<TAB>" is easier than "C:\Progr<TAB>\choc<TAB>"
- ygra 14y agoShow 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.
- niggler 14y agoWhen 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.
- ajanuary 14y agoReally? 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?
- niggler 14y agoVB.NET shows the behavior with Class Test Public Shared Sub Main() Console.WriteLine("GetCommandLineArgs: {0}", String.Join(", ", Environment.GetCommandLineArgs())) End Sub End Class