4 ms·

I'm confused. Is PowerShell 'recognized' as a shell? I thought only unix and unix-like shells would be covered. I wonder what the technical definition of a sh

by ldd 10y ago

I'm confused. Is PowerShell 'recognized' as a shell? I thought only unix and unix-like shells would be covered. I wonder what the technical definition of a shell is though. (genuinely curious, not trying to be snarky)

hoov 10y ago
It clearly doesn't cover "unix and unix-like" shells, since fish shell syntax isn't supported. It seems to be trying to be bash-compatible since it uses bashlex under the hood, but as another commented noticed, the bash parsing isn't perfect.
deleted 10y ago
[deleted]
arca_vorago 10y ago
>I'm confused. Is PowerShell 'recognized' as a shell? Yes, given the definiton of shell being a user interface to an operating system, typically command line, powershell is considered a shell and can function as one. For example, while many think of windows servers as being all gui, newer versions of windows (server) can be run entirely in cli mode with no gui via powershell, in which supposedly any management technique normally done through gui can be done through the ps cli. The main difference between nix shells and powershell is that the nix shells are text based, while powershell is object based due to it's .NET core. As a sysadmin who uses both bash and powershell, I have to say the more recent versions of powershell are quite powerful and a fresh breath of air to use in the normally stale windows world. Of course, I tend to use pywinrm to remotely run ps commands so I don't too dirty touching the tainted MS ecosystem. (That's my way of saying that while powershell is nice and a large improvement over batch command line files, bash is still the better one due to the underlying unix philosophy and the GNU ecosystem)
recursive 10y ago
It depends who's doing the recognizing. I don't see why it wouldn't. And I'm not sure where you got the idea that it was unix-likes only.
electricEmu 10y ago
Yes, it is recognized as a shell. The original description was listed as "explain any shell command". That was an erroneous title that's since been updated.

by ldd 10y ago

hoov 10y ago

It clearly doesn't cover "unix and unix-like" shells, since fish shell syntax isn't supported. It seems to be trying to be bash-compatible since it uses bashlex under the hood, but as another commented noticed, the bash parsing isn't perfect.

deleted 10y ago

[deleted]

arca_vorago 10y ago

>I'm confused. Is PowerShell 'recognized' as a shell? Yes, given the definiton of shell being a user interface to an operating system, typically command line, powershell is considered a shell and can function as one. For example, while many think of windows servers as being all gui, newer versions of windows (server) can be run entirely in cli mode with no gui via powershell, in which supposedly any management technique normally done through gui can be done through the ps cli. The main difference between nix shells and powershell is that the nix shells are text based, while powershell is object based due to it's .NET core. As a sysadmin who uses both bash and powershell, I have to say the more recent versions of powershell are quite powerful and a fresh breath of air to use in the normally stale windows world. Of course, I tend to use pywinrm to remotely run ps commands so I don't too dirty touching the tainted MS ecosystem. (That's my way of saying that while powershell is nice and a large improvement over batch command line files, bash is still the better one due to the underlying unix philosophy and the GNU ecosystem)

recursive 10y ago

It depends who's doing the recognizing. I don't see why it wouldn't. And I'm not sure where you got the idea that it was unix-likes only.

electricEmu 10y ago

Yes, it is recognized as a shell. The original description was listed as "explain any shell command". That was an erroneous title that's since been updated.