After spending some time to debug it, I discovered that the project cannot be compiled on MacOS if -DCLANG_SUFFIX="-9" is passed. I have llvm@9 installed from brew and it gives the following error:

-- The C compiler identification is Clang 9.0.1
-- The CXX compiler identification is unknown
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for work

It's common when writing scripts that install or configure things to need input from the user (at a minimum, something like 'Press Enter to continue'; at a maximum, to be able to prompt the user for input, with an optional default value, and return that value).

Let's use this issue to design how that would look, and I invite suggestions!

Issue #110 introduced type aliases to Mun - on a file-level. We want to extend this, such that - similar to Rust - Mun can support type aliases in a local scope:

type OtherTypeName = i32;
fn main() {
    type Typename = OtherTypeName; // Type alias in local scope
    let a: Ty

Is there a convenient way to format a FileStatus? I am looking for an interactive equivalent of the Unix ls -l, and it seems that I have to write this from scratch.

FWIW, here is my current attempt -- I'm sure it can be improved.

Describe the bug
You can't call a variable banIP or banSerial without getting an output on the server console/log.

To reproduce

-- serverside
banIP = "192.168.1.69"

Run that code and you will see and output similar to this:

[Server] banIP no longer works. Please manually update this. Refer to the wiki for details

Expected behaviour
It should only tell you tha

The CMakeLists files of this project is kinda messy, mostly due to my limited understanding of the topic.

So they definitely need to be cleaned up at some point

Apart from jbang help and the examples of jbang use given in the readme, it would be great to have:

1. A documentation - Picocli generated ?
2. A cheat sheet usable with https://github.com/cheat/cheat

The second one is very efficient, as you document only the most frequent usages of a command, so you find very quickly the command you need.

For example, the LSP could expose commands to run, check, or test the current code by sharing some code with rune-cli.

Potentially has some overlap with DAP, for debugging capabilities.