docs: standardize on "layout generator"

This is likely more clear than "layout client" to most users.
This commit is contained in:
Isaac Freund 2021-10-31 22:32:59 +01:00
parent 8134b81283
commit 8757644b2a
No known key found for this signature in database
GPG Key ID: 86DED400DDFD7A11
6 changed files with 8 additions and 8 deletions

View File

@ -56,7 +56,7 @@ complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a toggle-fu
complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a zoom -d 'Bump the focused view to the top of the layout stack'
complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a default-layout -d 'Set the layout namespace to be used by all outputs by default.'
complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a output-layout -d 'Set the layout namespace of currently focused output.'
complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a send-layout-cmd -d 'Send command to the layout client on the currently focused output with the given namespace'
complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a send-layout-cmd -d 'Send command to the layout generator on the currently focused output with the given namespace'
# Tag managements
complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a set-focused-tags -d 'Show views with tags corresponding to the set bits of tags'
complete -c riverctl -x -n '__fish_riverctl_complete_no_subcommand' -a set-view-tags -d 'Assign the currently focused view the tags corresponding to the set bits of tags'

View File

@ -25,7 +25,7 @@ _riverctl_subcommands()
'zoom:Bump the focused view to the top of the layout stack'
'default-layout:Set the layout namespace to be used by all outputs by default.'
'output-layout:Set the layout namespace of currently focused output.'
'send-layout-cmd:Send command to the layout client on the currently focused output with matching namespace'
'send-layout-cmd:Send command to the layout generator on the currently focused output with matching namespace'
# Tag management
'set-focused-tags:Show views with tags corresponding to the set bits of tags'
'set-view-tags:Assign the currently focused view the tags corresponding to the set bits of tags'

View File

@ -99,9 +99,9 @@ over the Wayland protocol.
the value set with *default-layout* if any.
*send-layout-cmd* _namespace_ _command_
Send _command_ to the layout client on the currently focused output
with the given _namespace_, if any. What commands a layout client
understands depends on the layout client. For rivertile, see the
Send _command_ to the layout generator on the currently focused output
with the given _namespace_, if any. What commands a layout generator
understands depends on the layout generator. For rivertile, see the
documentation in the *rivertile*(1) man page.
## TAG MANAGEMENT

View File

@ -10,7 +10,7 @@ rivertile - tiled layout generator for river
# DESCRIPTION
*rivertile* is a layout client for *river*(1). It provides a simple tiled
*rivertile* is a layout generator for *river*(1). It provides a simple tiled
layout with split main/secondary stacks. The initial state may be configured
with various options passed on startup. Some values may additionally be
modified while rivertile is running with the help of *riverctl*(1).

View File

@ -674,7 +674,7 @@ pub fn enterMode(self: *Self, mode: std.meta.Tag((Mode)), view: *View) void {
}
// Automatically float all views being moved by the pointer, if
// their dimensions are set by a layout client. If however the views
// their dimensions are set by a layout generator. If however the views
// are unarranged, leave them as non-floating so the next active
// layout can affect them.
if (!view.current.float and view.output.current.layout != null) {

View File

@ -137,7 +137,7 @@ pub fn resize(
fn apply(view: *View) void {
// Set the view to floating but keep the position and dimensions, if their
// dimensions are set by a layout client. If however the views are
// dimensions are set by a layout generator. If however the views are
// unarranged, leave them as non-floating so the next active layout can
// affect them.
if (view.output.pending.layout != null)