Merge pull request #28 from LeonardoTrapani/docs/push-to-talk-bindings

document push-to-talk keybinding patterns
This commit is contained in:
Leonardo Trapani
2026-04-17 16:51:50 +02:00
committed by GitHub
2 changed files with 69 additions and 0 deletions
+34
View File
@@ -83,6 +83,8 @@ systemctl --user enable --now hyprvoice.service
bind = SUPER, R, exec, hyprvoice toggle bind = SUPER, R, exec, hyprvoice toggle
``` ```
See [Hyprland Keybindings](#hyprland-keybindings) for push-to-talk and other patterns.
4. Test voice input: 4. Test voice input:
```bash ```bash
@@ -91,6 +93,38 @@ hyprvoice toggle
Run `hyprvoice configure` anytime for advanced settings. Run `hyprvoice configure` anytime for advanced settings.
## Hyprland Keybindings
### Simple toggle
```bash
# ~/.config/hypr/hyprland.conf
bind = SUPER, R, exec, hyprvoice toggle
```
Each press toggles between recording and idle.
### Push-to-talk (hold-to-record)
Combine both bind types to get hold-to-record behavior — press to start, release to stop:
```bash
# ~/.config/hypr/hyprland.conf
bind = SUPER, R, exec, hyprvoice toggle # key down → start recording
bindr = SUPER, R, exec, hyprvoice toggle # key up → stop and transcribe
```
This gives a walkie-talkie feel: hold the key while speaking, release when done. The daemon receives two `toggle` commands — the first starts recording, the second stops it and triggers transcription.
### `bind` vs `bindr`
| Keyword | Fires on |
|---------|----------|
| `bind` | Key **press** (down) |
| `bindr` | Key **release** (up) |
With `bindr`, modifier keys (SUPER, CTRL, etc.) are fully released before the command executes. This can prevent modifiers from interfering with text injection.
## Commands ## Commands
### Core CLI ### Core CLI
+35
View File
@@ -21,6 +21,7 @@ Configuration is stored in `~/.config/hyprvoice/config.toml` and changes are app
## Table of Contents ## Table of Contents
- [Hyprland Keybinding Patterns](#hyprland-keybinding-patterns)
- [Unified Provider System](#unified-provider-system) - [Unified Provider System](#unified-provider-system)
- [Transcription Providers](#transcription-providers) - [Transcription Providers](#transcription-providers)
- [Cloud Providers](#cloud-providers) - [Cloud Providers](#cloud-providers)
@@ -36,6 +37,40 @@ Configuration is stored in `~/.config/hyprvoice/config.toml` and changes are app
- [Example Configurations](#example-configurations) - [Example Configurations](#example-configurations)
- [Legacy Configs](#legacy-configs) - [Legacy Configs](#legacy-configs)
## Hyprland Keybinding Patterns
Hyprvoice is triggered via Hyprland keybindings. The bind type you choose affects reliability and workflow.
### Simple toggle
```bash
# ~/.config/hypr/hyprland.conf
bind = SUPER, R, exec, hyprvoice toggle
```
Each press toggles between recording and idle.
### Push-to-talk (hold-to-record)
Pair `bind` (press) with `bindr` (release) on the same key for hold-to-record:
```bash
# ~/.config/hypr/hyprland.conf
bind = SUPER, R, exec, hyprvoice toggle # key down → start recording
bindr = SUPER, R, exec, hyprvoice toggle # key up → stop and transcribe
```
Hold the key while speaking, release when done. Both lines send `toggle` to the daemon — the first starts the pipeline, the second stops it. Because the stop fires on release, modifiers are clean for injection.
### `bind` vs `bindr`
| Keyword | Fires on |
|---------|----------|
| `bind` | Key **press** (down) |
| `bindr` | Key **release** (up) |
With `bindr`, modifier keys (SUPER, CTRL, etc.) are fully released before the command executes. This can prevent modifiers from interfering with text injection.
## Unified Provider System ## Unified Provider System
Hyprvoice uses a unified provider system where API keys are configured once and shared between transcription and LLM features: Hyprvoice uses a unified provider system where API keys are configured once and shared between transcription and LLM features: