Whisper/Shout as RPC commands

[zerodegress]

Context

There is no global shortcut key support under Linux Wayland, so I hope to rely on RPC for "Whisper/Shout" operations.

Description

Add an RPC parameter, such as “whisper,” along with an additional parameter to specify the target channel for the whisper, for example, “Current”.

Mumble component

Client

OS-specific?

No

Additional information

No response

[Hartmnt]

Mhh, I think that would require to implement a startwhisper and stopwhisper rpc command. But overall I think this is a reasonable request.

[Krzmbrzl]

The difficulty will be how one implements setup for the target. This requires knowledge of what is on the server, which I don't think is easily accessible from outside Mumble (where the RPC request is coming from) 🤔

[Hartmnt]

The difficulty will be how one implements setup for the target. This requires knowledge of what is on the server, which I don't think is easily accessible from outside Mumble (where the RPC request is coming from) 🤔

One possibility would be to just forward the CLI argument as a string without trying to do something fancy at all on CLI level. The main client then resolves the string to a channel/user and starts to whisper.
And stopwhisper would then just stop either any whisper, or you'd have to provide the same string as before to stop just that whisper.

That begs the question would we want/need multiple whisper targets on CLI level?

[Krzmbrzl]

And stopwhisper would then just stop either any whisper, or you'd have to provide the same string as before to stop just that whisper.

As it is not possible for multiple whispers to happen at the same time, I don't think stopwhisper would need any argument 🤔

That begs the question would we want/need multiple whisper targets on CLI level?

Only in the sense of being able to specify multiple users/channels when starting a whisper/shout, I'd say.