Minor doc adjustments

main
Tassilo Horn 3 years ago
parent 5682d3dadc
commit 23ca1f7f2f
  1. 31
      README.md
  2. 9
      swayr/NEWS.md

@ -110,7 +110,7 @@ by the shortcut. The following shortcuts are supported.
`w:<input>` would do. `w:<input>` would do.
#### Cycling commands #### <a id="swayr-cycling-commands">Cycling commands</a>
Those commands cycle through (a subset of windows) in last-recently-used order. Those commands cycle through (a subset of windows) in last-recently-used order.
@ -173,11 +173,12 @@ These commands change the layout of the current workspace.
* `execute-swayr-command` displays all commands above and executes the selected * `execute-swayr-command` displays all commands above and executes the selected
one. (This is useful for accessing swayr commands which are not bound to a one. (This is useful for accessing swayr commands which are not bound to a
key.) key.)
* `nop` (unsurprisingly) does nothing, the command can be used to break out of a * `nop` (unsurprisingly) does nothing, the command can be used to break out of
sequence of [window cycling commands](#cycling-commands). The LRU window order a sequence of [window cycling commands](#swayr-cycling-commands). The LRU
is frozen when the first cycling command is processed and remains so until a window order is frozen when the first cycling command is processed and
non-cycling command is received. The `nop` command can conveniently serve to remains so until a non-cycling command is received. The `nop` command can
interrupt a sequence without having any other side effects. conveniently serve to interrupt a sequence without having any other side
effects.
### <a id="swayr-screenshots">Screenshots</a> ### <a id="swayr-screenshots">Screenshots</a>
@ -275,10 +276,11 @@ bindsym $mod+Shift+c exec env RUST_BACKTRACE=1 \
Of course, configure the keys to your liking. Again, enabling rust backtraces Of course, configure the keys to your liking. Again, enabling rust backtraces
and logging are optional. and logging are optional.
Pending a fix for [Sway issue 6456](https://github.com/swaywm/sway/issues/6456), Pending a fix for [Sway issue
it will be possible to close a sequence of window cycling commands using #6456](https://github.com/swaywm/sway/issues/6456), it will be possible to
a `nop` command bound to the release of the `$mod` key. Assuming your `$mod` close a sequence of [window cycling commands](#swayr-cycling-commands) using a
is bound to `Super_L` it could look something like this: `nop` command bound to the release of the `$mod` key. Assuming your `$mod` is
bound to `Super_L` it could look something like this:
``` ```
bindsym --release Super_L exec env RUST_BACKTRACE=1 \ bindsym --release Super_L exec env RUST_BACKTRACE=1 \
@ -476,10 +478,11 @@ are a workaround and wouldn't be required if there were resize-events.
#### The focus section #### The focus section
In the `[focus]` section, you can configure the amount of time a window In the `[focus]` section, you can configure the amount of time a window has to
has to keep the focus in order to affect the LRU order. If a given window keep the focus in order to affect the LRU order, the `lockin_delay`. If a
is only briefly focused, e.g. moving the mouse over it on the way to given window is only briefly focused, e.g., by moving the mouse over it on the
another window, then its position in the LRU order will not be modified. way to another window with sway's `focus_follows_mouse` set to `yes` or
`always`, then its position in the LRU order will not be modified.
### <a id="swayr-version-changes">Version changes</a> ### <a id="swayr-version-changes">Version changes</a>

@ -2,10 +2,11 @@ swayr v0.18.0
============= =============
- The LRU window order will no longer be immediately updated when there is a - The LRU window order will no longer be immediately updated when there is a
focus change. Instead there is now a short (configurable) delay before the focus change. Instead there is now a short (configurable) delay
update. The user-visible change is that quickly moving over windows with the (`focus.lockin_delay`) before the update. The user-visible change is that
mouse, or moving through them using keyboard navigation, will only register quickly moving over windows with the mouse, or moving through them using
the start and destination windows in the LRU sequence. keyboard navigation, will only register the start and destination windows in
the LRU sequence.
- A `nop` command can be used to interrupt a sequence of window-cycling - A `nop` command can be used to interrupt a sequence of window-cycling
commands. commands.

Loading…
Cancel
Save