starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

Whisper/Shout as RPC commands #3056

New issue

Open

opened 2026-02-20 22:17:19 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 22:17:19 -05:00

Owner

Originally created by @zerodegress on GitHub (Oct 19, 2025).

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?

Additional information

No response

Originally created by @zerodegress on GitHub (Oct 19, 2025). ### 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_

deekerman added the

client

feature-request

labels

2026-02-20 22:17:19 -05:00

deekerman commented

2026-02-20 22:17:22 -05:00

Author

Owner

@Hartmnt commented on GitHub (Oct 19, 2025):

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

@Hartmnt commented on GitHub (Oct 19, 2025): Mhh, I think that would require to implement a ``startwhisper`` and ``stopwhisper`` rpc command. But overall I think this is a reasonable request.

deekerman commented

2026-02-20 22:17:22 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Oct 21, 2025):

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) 🤔

@Krzmbrzl commented on GitHub (Oct 21, 2025): 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) 🤔

deekerman commented

2026-02-20 22:17:22 -05:00

Author

Owner

@Hartmnt commented on GitHub (Oct 21, 2025):

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?

@Hartmnt commented on GitHub (Oct 21, 2025): > 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?

deekerman commented

2026-02-20 22:17:22 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Oct 21, 2025):

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.

@Krzmbrzl commented on GitHub (Oct 21, 2025): > 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.