237dmitry

> Since you know it's a secure string, it shoud not be printed in the error You can not type `System.Secure.SecureString` as plain text. Doesn't it bother you that the...

There is default solution about entering password/ `Read-Host -AsSecureString` ```powershell $pass = Read-Host "Enter password" -AsSecureString $pass # System.Security.SecureString ConvertFrom-SecureString $pass -Asplaintext ``` This is the basic example. You can...

I think that the definition of parameter expected single argument ```powershell enum SomeEnum {one; two; three} & { param([SomeEnum[]] $someEnumVal) $someEnumVal } -SomeEnum one, two, three # 0,1,2 ```

I think errors rise after executing expression: ``` iex "gi noexist" iex "gi noexist -ea 0" ```

It would be better to replace Windows.Forms with cross-platformed TUI-toolkit out of the box.

Because without this named parameter you cannot execute `Set-Location` in `Stack` context.

It works inside pwsh-session:  PS. I think bash can't interpret grave character correctly as it's service one.

In my environment all works ``` dir -s -file *paper* # returned all files like Wallpaper-##.ext ```

zip?

> and doesn't register as an installed program What is the difference? I always install from archive on linux (because I don't trust AUR)