Quick start: install, upgrade with xbps, first run, push-to-talk, toggle, niri, debug.
New GPU and CUDA section: the published package accelerates with Vulkan and CPU; CUDA is only a local-build or user-environment option.
The old project name now appears once, in the Origin credit line (inspired by).
tests/test_rename_sweep.py records the new credit line.
- Quick start: install, upgrade with xbps, first run, push-to-talk, toggle, niri, debug.
- New GPU and CUDA section: the published package accelerates with Vulkan and CPU; CUDA is only a local-build or user-environment option.
- The old project name now appears once, in the Origin credit line (inspired by).
- tests/test_rename_sweep.py records the new credit line.
Quick start with upgrade, first run, dictation, niri and debug steps. New GPU and CUDA section stating that the published package uses Vulkan and CPU and that CUDA is a local-build option. The old name now appears only in the Origin credit line.
The intro line links to [Origin](#origin), but the section heading was renamed to ## Origin — GitHub anchors for ## Origin are #origin, so this actually resolves correctly. However, the features bullet links to [GPU and CUDA](#gpu-and-cuda) while the new section heading is ## GPU and CUDA, which produces anchor #gpu-and-cuda — this also matches. No issue after verification; disregard if anchor generation differs. (No concrete broken link found.)
No account is required. Models download once. After that, speech-to-text stays on your machine. It is built for Void Linux, with niri and the Dank Material Shell in mind, and is inspired by an earlier project credited under [Origin](#origin).
The migration section previously listed the exact leftover launcher paths (~/.local/share/applications/vocalinux.desktop, ~/.local/bin/vocalinux, ~/.local/bin/vocalinux-gui) with copy-pasteable rm commands. The rewritten "Leftover launchers from an earlier install" section only says to "remove the ones it names yourself," so a user whose notice doesn't fire (or who reads the README before launching) no longer has the concrete paths to act on. Consider keeping the example paths alongside the new wording.
### Leftover launchers from an earlier install
Launchers left by an earlier install of the upstream project can point at a Python
environment that no longer exists. They start nothing, yet they appear next to
Voculinux in the application menu. Voculinux logs and shows one notice that names
those files. It never deletes or changes them, so remove the ones it names
yourself. Keep any launcher that still starts a working install.
## PR Reviewer Guide 🔍
<!-- pr-agent:review:full -->
Here are some key observations to aid the review process:
<table>
<tr><td>⏱️ <strong>Estimated effort to review</strong>: 2 🔵🔵⚪⚪⚪</td></tr>
<tr><td>🧪 <strong>PR contains tests</strong></td></tr>
<tr><td>🔒 <strong>No security concerns identified</strong></td></tr>
<tr><td>⚡ <strong>Recommended focus areas for review</strong><br><br>
<details><summary><a href='https://git.bongbetic.com/xavierk/voculinux/src/branch/docs/readme-usage/README.md#L22-L22'><strong>Broken anchor link</strong></a>
The intro line links to `[Origin](#origin)`, but the section heading was renamed to `## Origin` — GitHub anchors for `## Origin` are `#origin`, so this actually resolves correctly. However, the features bullet links to `[GPU and CUDA](#gpu-and-cuda)` while the new section heading is `## GPU and CUDA`, which produces anchor `#gpu-and-cuda` — this also matches. No issue after verification; disregard if anchor generation differs. (No concrete broken link found.)
</summary>
```markdown
No account is required. Models download once. After that, speech-to-text stays on your machine. It is built for Void Linux, with niri and the Dank Material Shell in mind, and is inspired by an earlier project credited under [Origin](#origin).
```
</details>
<details><summary><a href='https://git.bongbetic.com/xavierk/voculinux/src/branch/docs/readme-usage/README.md#L193-L199'><strong>Removed concrete examples</strong></a>
The migration section previously listed the exact leftover launcher paths (`~/.local/share/applications/vocalinux.desktop`, `~/.local/bin/vocalinux`, `~/.local/bin/vocalinux-gui`) with copy-pasteable `rm` commands. The rewritten "Leftover launchers from an earlier install" section only says to "remove the ones it names yourself," so a user whose notice doesn't fire (or who reads the README before launching) no longer has the concrete paths to act on. Consider keeping the example paths alongside the new wording.
</summary>
```markdown
### Leftover launchers from an earlier install
Launchers left by an earlier install of the upstream project can point at a Python
environment that no longer exists. They start nothing, yet they appear next to
Voculinux in the application menu. Voculinux logs and shows one notice that names
those files. It never deletes or changes them, so remove the ones it names
yourself. Keep any launcher that still starts a working install.
```
</details>
</td></tr>
</table>
xavierk
merged commit 808bd17704 into main2026-11-07 03:00:25 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
PR Reviewer Guide 🔍
Here are some key observations to aid the review process:
Broken anchor link
The intro line links to
[Origin](#origin), but the section heading was renamed to## Origin— GitHub anchors for## Originare#origin, so this actually resolves correctly. However, the features bullet links to[GPU and CUDA](#gpu-and-cuda)while the new section heading is## GPU and CUDA, which produces anchor#gpu-and-cuda— this also matches. No issue after verification; disregard if anchor generation differs. (No concrete broken link found.)Removed concrete examples
The migration section previously listed the exact leftover launcher paths (
~/.local/share/applications/vocalinux.desktop,~/.local/bin/vocalinux,~/.local/bin/vocalinux-gui) with copy-pasteablermcommands. The rewritten "Leftover launchers from an earlier install" section only says to "remove the ones it names yourself," so a user whose notice doesn't fire (or who reads the README before launching) no longer has the concrete paths to act on. Consider keeping the example paths alongside the new wording.