MOULTI

Moulti changes the way your shell scripts (bash, zsh, etc.) display their output in your terminal. Moulti enables you to assign the numerous lines emitted by your scripts to "steps", i.e. visual, collapsible blocks featuring their own title and color.

Here is how upgrading a Debian system looks like with Moulti:

Interested? Run this demo in a container using docker or podman

Moulti is a tool meant for people who write and execute shell scripts. Specifically, if you find yourself scrolling up your terminal to ensure everything went fine while your script is still running, then Moulti is made for you.

How?

Synopsis:

1. Start a Moulti instance: moulti init
2. Add a step: moulti step add step_name --title='some clever title here'
3. Fill it: whatever_your_script_does | moulti pass step_name
4. Repeat #2 and #3 until your script is done.

Learn how to leverage Moulti by jumping to its Documentation.

Features

As shown in the demo, Moulti enables user interactions through questions:

Moulti also features: - a progress bar: documentation - programmatic scrolling: documentation - an askpass helper named moulti-askpass: documentation

When it comes to look and feel, Moulti can be customised:

• through moulti set: define whether Moulti steps flow up or down: documentation
• through Textual CSS (TCSS): documentation
• through ANSI themes: documentation

Implementation

Moulti is written in Python and leverages Textual, along with Pyperclip and argcomplete.

Inspiration

Moulti remained a mere idea for a significant time (possibly years).

The idea of driving TUI elements from scripts obviously comes from tools like dialog and whiptail.

At some point, the author stumbled upon multiplex, which is probably the closest thing to Moulti. multiplex was deemed unsatisfying on multiple points (including architecture) and that prompted the development of Moulti.

procmux is also similar to Moulti but did not affect its development.

Acknowledgments

The Textual framework helped a lot, so kudos to the Textual team, and specifically to: - Will McGugan for creating it - Dave Pearson for his regular help and feedback about Textual issues