From 78a46c316a2c220c96c377ffaaa090c16668fd4f Mon Sep 17 00:00:00 2001 From: Isaac Freund Date: Wed, 29 Dec 2021 21:13:32 +0000 Subject: input-inhibit: remove support for protocol The only valid use-case for this as far as I'm concerned is lockscreens, which will now be supported through ext-session-lock-v1. --- doc/riverctl.1.scd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/riverctl.1.scd') diff --git a/doc/riverctl.1.scd b/doc/riverctl.1.scd index d98aafe..5fb392e 100644 --- a/doc/riverctl.1.scd +++ b/doc/riverctl.1.scd @@ -157,8 +157,8 @@ are ignored by river. Mappings are modal in river. Each mapping is associated with a mode and is only active while in that mode. There are two special modes: "normal" and "locked". The normal mode is the initial mode on startup. The locked mode -is automatically entered while an input inhibitor (such as a lockscreen) -is active. It cannot be entered or exited manually. +is automatically entered while a lock screen is active. It cannot be entered +or exited manually. The following modifiers are available for use in mappings: -- cgit v1.2.3