UX: bloop help is not exteremely friendly

[svalaskevicius]

❯ bloop --help
Usage: bloop [options]
Interact with Bloop (the build server) or check its status.

This sub-command allows to check the current status of Bloop.
If Bloop isn't currently running, it will be started.

Help options:
  --usage            Print usage and exit
  -h, -help, --help  Print help message and exit

Other options:
  -v, --verbose                     Increase verbosity (can be specified multiple times)
  -q, --quiet                       Decrease verbosity
  --progress                        Use progress bars
  --home, --home-directory string?
  --java-home path                  Set the Java home directory
  -j, --jvm jvm-name                Use a specific JVM, such as `14`, `adopt:11`, or `graalvm:21`, or `system`

❯ bloop --usage
Usage: bloop [options]

❯ bloop --usage -v
Usage: bloop [options]

what options?

[svalaskevicius]

to add: I expected to find how to stop the current running server.. trying to find that on internetz still (bloop start exists, but stop does not)

[tgodzik]

Thanks for reporting! I think this can use some improvements. bloop exit is what you're looking for.

We use case-app so it's possible to improve it somewhere around

bloop/cli/src/main/scala/bloop/cli/options/DefaultOptions.scala

Line 22 in f799e88

|If Bloop isn't currently running, it will be started.""".stripMargin

if anyone is interested.

Auto completions should however work, which might also be useful.