ba9df86472
main is a better term to use here for several reasons: 1. It is more accurate: "master" implies that the designated views have some kind of control over the other views, which is not the case. "main" better expresses that the difference between the "main" view and others is one of importance/focus. 2. It is a shorter word. 2 whole characters saved! 3. It reduces the chance of future development time being lost to good-intentioned people complaining about usage of the word master as has recently happened with regards to the default git branch name.
45 lines
969 B
Markdown
45 lines
969 B
Markdown
RIVERTILE(1) "github.com/ifreund/river" "General Commands Manual"
|
|
|
|
# NAME
|
|
|
|
rivertile - Tiled layout generator for river
|
|
|
|
# SYNOPSIS
|
|
|
|
*rivertile* *left*|*right*|*top*|*bottom* [args passed by river]
|
|
|
|
# DESCRIPTION
|
|
|
|
*rivertile* is a layout generator for river. It produces tiled layouts with
|
|
split main/secondary stacks in four configurable orientations.
|
|
|
|
# OPTIONS
|
|
|
|
*left*
|
|
Place the main stack on the left side of the output.
|
|
|
|
*right*
|
|
Place the main stack on the right side of the output.
|
|
|
|
*top*
|
|
Place the main stack at the top of the output.
|
|
|
|
*bottom*
|
|
Place the main stack at the bottom of the output.
|
|
|
|
# EXAMPLE
|
|
|
|
Set river's layout to *rivertile*'s *left* layout using riverctl
|
|
|
|
riverctl layout rivertile left
|
|
|
|
# AUTHORS
|
|
|
|
Maintained by Isaac Freund <ifreund@ifreund.xyz> who is assisted by open
|
|
source contributors. For more information about river's development, see
|
|
<https://github.com/ifreund/river>.
|
|
|
|
# SEE ALSO
|
|
|
|
*river-layouts*(7), *river*(1), *riverctl*(1)
|