Hrxn/Pwsh

Some PowerShell scripts - primarily for interactive terminal usage.

Please be aware:
This is still a work-in-progress.
Some of these were used in learning PowerShell in the first place.
All usual disclaimers apply etc. pp.

A couple of notes:

Almost all of these are based on old Windows CMD scripts, sometimes also simply known as Batchfiles.

Rewriting my old stuff in PowerShell seemed like a sane choice in order to make this all portable and ensure it's future proof, at least somewhat.

I strive to be somewhat consistent here in script design and idiomatic language utilization, but that is not an absolute priority. All of these scripts are designed to be self-contained, i.e. they do not depend on each other, or on other PowerShell Modules, or Components etc.
The one glaring exception is obviously scripts that are made to run other applications, like FFmpeg for example. But I've started to add dependency checks in such cases. God knows who might need them..
Please note that I'm targeting only fairly recent versions of PowerShell now. In other words, PowerShell Core only, or better. Version 7.2 is considered LTS, so that will be used as reference in the future.

Wait... No Module?

Yes, this is by design.

While PowerShell has usually been considered as a shell designed for scripting and automation, it is actually also a pretty decent interactive shell.

The primary intended purpose of this entire collection is usage in an interactive shell environment. Considering that startup and initialization time is a longstanding issue with PowerShell, the priority in this case here seems quite clear. PowerShell includes many integrated modules that are not loaded by default and are only delay-loaded optionally.

Goals:

• Make terminal life easier and more joyful.
• Optimize for interactive usage.
• Cross-platform support.
  • To the extent that it's even possible at all. Some limitations still apply, obviously.
  • All platforms that are not Windows should be considered untested so far.
• Scratching my own itch.
  • The reason this came into existence.
• Optimize for portability.

Non-Goals:

• Replicating functionality that already exists within the shell (poof, so many old scripts not needed anymore).
• Competing with already established solutions or applications that already fit their purpose very well and solve their tasks.
• GUI usage, even in the distant future, although possible with PowerShell.
• Ugly optimizations and performance hacks.
• Excessive hand-holding.
  • I'm serious, do not expect to be spoonfed here. I'm trying to make these easily usable, but there is a line.
    If you don't know how to use CLI programs, or how to properly set up your environment variables, you are wrong here.

Thank you for your attention.