237dmitry
237dmitry
> why do you think that Bash syntax is in any way relevant here? Because in bash `/bin/echo *` outputs list of files. You escaped ``` `* ``` and `/bin/echo`...
> It is not /bin/echo that performs the globbing /bin/echo receives parameter that already globbed. Isn't it true?
> should be equivalent to the quoted forms, but isn't. I'm already confused with escaping. ```powershell PS > /bin/echo 1`n2 1 2 PS > Start-Process /bin/echo -ArgumentList 1`n2 1 2...
Is this for 7.3.0 ? In 7.2.6 no errors. 
Since basically the output to the console is from the prompt function, what happens (with subject) if you do not delete the profile, but reset the prompt function? And is...
```powershell PS > [Environment]::SetEnvironmentVariable OverloadDefinitions ------------------- static void SetEnvironmentVariable(string variable, string value) static void SetEnvironmentVariable(string variable, string value, System.EnvironmentVariableTarget target) PS > [Environment]::GetEnvironmentVariable OverloadDefinitions ------------------- static string GetEnvironmentVariable(string variable) static...
> users are confused by using dotnet objects I disagree with this statement. I very rarely change system and user environment variables, mostly in the current session, `env:` and `$env`...
In my opinion, such a simplified syntax as `function ($arg1, $arg2) {}` is used for embedding in scripts when the type of output data is precisely known. This is not...
```powershell Get-ItemProperty -LiteralPath (Read-Host).Replace('"','') Get-ItemProperty -LiteralPath (Read-Host).Replace('"',$null) Get-ItemProperty -LiteralPath (Read-Host).Replace("`"","") # also working ```
