docs: standardize on "layout generator"
This is likely more clear than "layout client" to most users.
This commit is contained in:
@ -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
|
||||
|
@ -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).
|
||||
|
Reference in New Issue
Block a user