Batsh VS PowerShell

https://github.com/batsh-dev-team/Batsh

https://github.com/tdenniston/bish

(Just fyi. I've been collecting links to similar things because of Reasons).

I wish there was a nicer shell scripting language that simply transpiled to Bash and would generate all this boilerplate code for me. There is https://batsh.org/ which has a nice syntax but it doesn't even support pipes or redirection, making it pretty worthless for shell scripting. I haven't found any other such scripting languages.

There are some languages that compile into bash like Batch. Shell commands can also be called from Python code using this (never tried it): https://plumbum.readthedocs.io/en/latest/index.html

Maybe https://github.com/batsh-dev-team/Batsh

Not really what you're asking for, but a language that compiles to bash for portability reminded me of Batsh [0], a C-like language that compiles to bash for Linux/Mac and batch for Windows.

[0] https://github.com/batsh-dev-team/Batsh

There used to be something called Batsh as well but no longer seems to be actively developed

There are a couple projects that provide a language that compiles to Bash, which gets around Oil's portability problem somewhat. Bish and Batsh come to mind.

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901

PowerShell is available on macOS and Linux as well (source on Github: https://github.com/PowerShell/PowerShell). It may not be as well-integrated with things like system services management, but the language still works well. You can still use all the command line tools you're used to on Linux, of course.

nushell does look interesting, though the lack of a .deb repository does put it pretty low on my to-do list.

Issue #7940 discusses potential improvements to array slicing.

Note: This can be problematic as it prevents upstream commands from running their end {} block. See here. The new clean {} block introduced in PowerShell v7.3 does not suffer from this issue.

Can you give an example of something that PS can do that is built-in for text processing, instead of a proprietary symbolic query language?

[1] https://github.com/PowerShell/PowerShell

https://github.com/PowerShell/PowerShell/blob/master/LICENSE... is the MIT license. (Microsoft supplies debs directly which may reduce the motivation for Debian to do so.)

Oh, heh, also https://github.com/PowerShell/PowerShell/blob/master/docs/bu... the build script is written in PowerShell, so there's a bootstrapping problem :-) (Debian has solved those before of course, but with community sentiment like the above maybe noone is motivated to bother.)

According to https://github.com/PowerShell/PowerShell/issues/19628, the default behaviour is invoked whenever the completion script returns no output. To attempt to do so, I tried exiting the script via returning an empty string, or using the return keyword to exit the script completely, unfortunately with no avail. Is there a technique to achieve what I want, and is there any documentation about it other than the official one? Thank you in advance.