docs(niri): state the first-run experience and refresh the layout map
AGENTS.md layout now lists app_identity, legacy_import, model_ladder, packaging/void, the perf protocol script, the Gitea workflows and the niri doc, as its own maintenance rule requires. USER_GUIDE orders Wayland autodetection wtype before ydotool, matching the decided ladder, and says the portal is never tried on niri. docs/NIRI.md states the niri first dictation (no prompt; typing goes direct through wtype; IBus excluded) and points to the GNOME and KDE section.
This commit is contained in:
@@ -57,6 +57,15 @@ under **Settings → Shortcuts**; with it off, remove the niri bind. A key
|
||||
claimed on both sides fires twice: the compositor toggles over D-Bus while
|
||||
the internal listener fires on its own.
|
||||
|
||||
## First dictation
|
||||
|
||||
There is no permission prompt on niri. The RemoteDesktop portal is never
|
||||
used there, because no portal backend implements it, so your first dictation
|
||||
types straight into the focused window through `wtype` with nothing to approve
|
||||
or deny. Do not pin `portal` as a niri recommendation. IBus is excluded on
|
||||
niri as well. The GNOME and KDE first-run behaviour is described in
|
||||
[USER_GUIDE.md](USER_GUIDE.md#first-dictation-on-niri-gnome-and-kde).
|
||||
|
||||
## Hold-to-talk stays in the app
|
||||
|
||||
A compositor bind only sends the key press; it never sees the release, so
|
||||
|
||||
+3
-2
@@ -343,8 +343,9 @@ in place and may select IBus. An explicit non-IBus pin (`portal`, `wtype`,
|
||||
|
||||
On Wayland, when IBus is not selected, autodetection tries the RemoteDesktop
|
||||
portal first -- it is the only injection path Wayland officially supports and
|
||||
it needs no uinput device or helper daemon -- then `ydotool`, `wtype`, and
|
||||
finally `xdotool` under XWayland.
|
||||
it needs no uinput device or helper daemon -- then direct typing with `wtype`,
|
||||
then the virtual-input tool `ydotool`, and finally `xdotool` under XWayland.
|
||||
On niri the portal is never tried, because no backend there implements it.
|
||||
|
||||
On X11 the injection tool is `xdotool` regardless of which non-`ibus` value you
|
||||
pin, so `xdotool` is the name to use there when IBus is unreliable in a
|
||||
|
||||
Reference in New Issue
Block a user