hyprctl should be more helpful discovering usage

[hholst80]

Description

[I] root@neo ~
# man hyprctl 
No manual entry for hyprctl
[I] root@neo ~ [16]
# 

[I] root@neo ~ [16]
# hyprctl --help
usage: hyprctl [(opt)flags] [command] [(opt)args]

commands:
    activewindow
    activeworkspace
    binds
    clients
    cursorpos
    devices
    dispatch
    getoption
    globalshortcuts
    hyprpaper
    instances
    keyword
    kill
    layers
    layouts
    monitors
    notify
    plugin
    reload
    setcursor
    seterror
    setprop
    splash
    switchxkblayout
    version
    workspacerules
    workspaces

flags:
    -j -> output in JSON
    --batch -> execute a batch of commands, separated by ';'
    --instance (-i) -> use a specific instance. Can be either signature or index in hyprctl instances (0, 1, etc)

[I] root@neo ~ [1]
# 

So far not terrible. But individual commands should help the user to explore and figure out the usage.

[vaxerski]

I mean that's what the wiki is for no?

[hholst80]

I think the CLI tooling should be helpful enough not to require me to have a working internet connection to do anything useful. For most commands it is sufficient to just give the command and it will emit some output. But to send a notification, I have to know the magic handshake. If I fail to provide the right format, the tool should tell me what the right format is.

[vaxerski]

fair enough I guess

[JPDucky]

I agree heavily with this, trying to figure out more advanced usage of hyprctl is a nightmare as the current given documentation does not go into much detail.

[vaxerski]

MRs welcome.