237dmitry
237dmitry
> Come on, how would pwsh work otherwise? I deleted the post almost immediately, but you managed to read it. )) I was misled that in [powershell-7.3.0-linux-x64.tar.gz](https://github.com/PowerShell/PowerShell/releases/download/v7.3.0/powershell-7.3.0-linux-x64.tar.gz) pwsh is not...
> Are sure you're calling script from bash? 
I agree with the issue, aliases are hard to distinguish in help topics. For myself, I wrote a simple function to find out the parameter aliases: ```powershell function Find-ParametersAliases {...
> [Alias('fpa')] I set the same alias in $profile )) This alias is obvious.
> personally I think that it's better to set it in the function definition rather than outside of it I agree, this function used to be a script.
```powershell ParserError: /data/0.ps1:1 Line | 1 | using assembly SomeAssembly.dll | ~~~~~~~~~~~~~~~~ | Cannot load assembly 'SomeAssembly.dll' ``` ```powershell Exception : Type : System.Management.Automation.ParseException Errors : Extent : SomeAssembly.dll ErrorId...
> but does NOT include any time when the system was suspended. Yes, after reboot values was identical, when I closed the lid of laptop for three minutes I got...
> we could add a workaround for Linux systems and use /proc/uptime This works. ```powershell $ [timespan]::FromMilliseconds(([int](gc /proc/uptime).Split()[0] * 1000)).ToString() 01:33:18 $ uptime -p up 1 hour, 33 minutes ```
```powershell $ $PSNativeCommandArgumentPassing = 'Legacy' $ /bin/echo a,$PShome a,/opt/microsoft/powershell/7 ``` But: ```powershell $ /bin/echo -foo=$PShome -foo=$PShome ```
After upgrading to `7.3.0` the problem is remained. On Windows is the same problem but non-integers are rounded to hundredths. ``` [pscustomobject] @{ 'a' = 1.0 'b' = 1.12 'c'...