aboutsummaryrefslogtreecommitdiff
path: root/ryudo.1.md
blob: 70310e114daf6b1ab2f21a259834b10412c0f045 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
ryudo(1) -- The floatiling window manager that flows
===

## SYNOPSIS

`ryudo` [ -font FONTNAME ] [ -term TERMPROG ] [ -virtuals NUMVIRTS ] [ -ffm ] [ -version ] [ exit | restart ]

## DESCRIPTION

Ryudo is a window manager for X which is a fork of `rio` from `plan9port` by Russ Cox, which is itself a fork of David Hogan's `9wm`. Ryudo aims to be a more dynamic and configurable window manager while keeping most of the behavior of Rio.

The `-font` option sets the font in ryudo's menu to FONTNAME, overriding the default/fallback list in the `config.h`. As in rio, this is an X11 font, not a Plan 9 font.

The `-term` option sets the default terminal emulator, overriding the builtin defaults of `urxvt`, `9term`, and `xterm`.

The `-virtuals` option sets the number of virtual desktops (an integer from 1 to 12). The default, and their names, is set in the `config.h`.

The `-ffm` option sets the focus model to "focus-follows-mouse", instead of "click-to-focus".

The `-version` option prints the current version to `stderr` and then exits.

If either `exit` or `restart` is given, the appropriate message is sent to an already-running `ryudo` instance to execute the named action.


## BUILDING AND INSTALLATION

Run the provided `build.sh` and `install.sh` scripts to build and install `ryudo`. If run as root, they will install the program and manual pages to the PLAN9 installation path and install the `startryudo` session wrapper to `/usr/bin/` and a `.desktop` file to `/usr/share/xsessions/` If run as a regular user, they will install the program to `~/bin/9/` and not install the manual pages, wrapper, or `.desktop` file.

Building requires `plan9port` and the `libX11` and `libXT` headers. Optionally, `libnotify` is used to show notifications when switching virtual desktops.

## CONFIGURATION

Many configuration options have been enabled as compile-time options configured in the `config.h` configuration file. The `config.def.h` file shipped with the source code documents all of the options and contains what I hope are sane defaults. If `config.h` does not exist in the source directory, it will be copied from `config.def.h` on build. After changing the configuration file, it is necessary to run the `build.sh` and/or `install.sh` script again and restart the program.

Session autostart programs can be placed in `~/.ryudorc`, and command line arguments to `ryudo` can be placed in `~/.ryudo.conf` -- these are sourced by `startryudo`.

## USAGE

Right-clicking on the desktop or an inactive window opens a menu with the following options (not all enabled by default):

- `New`: Create a terminal window. Press mouse button 3 where one corner of the new window's area should start, hold it down, and drag the mouse to the opposite corner. Release the button to draw the window. The new window will be made active. The terminal program is either specified by the `-term` runtime option or the first of whichever of `urxvt`, `9term`, or `xterm` is installed.
- `Reshape`: Change the size and location of a window. Click mouse button 3 in the window to be changed, then sweep out the new window geometry as in the `New` operation. The changed window is made active.
- `Move`: Change the location of a window. Press and hold mouse button 3 on the window to be moved, and then drag the window to its new position. The window is made active.
- `Maximize`: Not enabled by default. Click mouse button 3 on the window to maximize, and it will fill the entire screen and be made active.
- `Stick`: Not enabled by default. Click mouse button 3 on a window to toggle its stickiness. If sticky, it will be present on all virtual desktops. If made unsticky, the window will be restricted to the current virtual desktop.
- `Delete`: Closes a window. Click the window to close with mouse button 3. `SIGHUP` (hangup signal) is sent to all processes in the window's process group.
- `Hide`: Minimize a window. Click the window with mouse button 3. It will be hidden and its label truncated and appended to the menu. There is a compiled-in limit of 128 hidden windows.
- `LABEL`: Select any label after the `Hide` option to restore it to the current virtual desktop.

Windows may be arranged by dragging their borders. Mouse buttons 1 or 2 can be used to drag an individual side/corner of a window around, resizing it. Mouse button 3 can be used to move the whole window.

Mouse button 2 on the desktop or an inactive window opens the virtual desktop list.

Mouse button 1 focuses a window. The click is not transferred to the window (you can only interact with it once it has been made active).

Alt-Tab cycles focus through all windows on the current desktop.

The following operations are bindable to key combinations (shown are the default bindings):

- `Launch` (Super + /): Open a new terminal in the center of the screen and make it active.
- `Reshape` (Super + R): Initiate a reshape operation as if the `Reshape` option was selected in the menu and the currently active window selected for the operation.
- `Move` (Super + V): Initiate a move operation as if the `Move` option was selected from the menu and the currently active window selected for the operation.
- `Maximize` (Super + M): Maximize the currently active window.
- `Hide` (Super + I): Minimize the currently active window.
- `Unhide` (Super + U): Restore the most recently minimized window.
- `Delete` (Super + D): Close the currently active window.
- `Stick` (Super + S): Toggle stickiness of the currently active window.
- `Zoom` (Super + Z): Toggle zoom mode. In zoom mode, the currently active window is maximized, new windows are opened maximized, and using Alt-Tab to switch to another window maximizes it.
- `Tile Left` (Super + H): Tile the currently active window to fill the left half of the screen.
- `Tile Right` (Super + L): Tile the currently active window to fill the right half of the screen.
- `Tile Top` (Super + K): Tile the currently active window to fill the top half of the screen.
- `Tile Bottom` (Super + J): Tile the currently active window to fill the bottom half of the screen.
- `Tile Top-Left` (Super + Q): Tile the currently active window to fill the top-left quarter of the screen.
- `Tile Bottom-Left` (Super + W): Tile the currently active window to fill the bottom-left quarter of the screen.
- `Tile Bottom-Right` (Super + O): Tile the currently active window to fill the bottom-right quarter of the screen.
- `Tile Top-Right` (Super + P): Tile the currently active window to fill the top-right quarter of the screen.
- `Center` (Super + C): Center the currently active window (primary geometry preference).
- `Center/Alternate` (Super + Shift + C): Center the currently active window (alternate geometry preference).

## BUGS AND CAVEATS

Multimonitor output is not currently supported -- the whole "screen" (collection of active monitors) is treated as one monitor, and keybinds and automatic window placement will not work properly.

Click events don't pass through when clicking to activate a window.

Clicking mouse button 2/3 on an inactive window brings up the Button 2/3 Menu instead of focusing the window. I personally sometimes find this behavior useful.

Programs that expect to run fullscreen will probably just open in a window the size of whatever resolution they expect to run at. Depending on the implementation, they may respond well to being maximized or you may have to change your screen resolution manually before doing so.

Fullscreen Virtualbox VM windows are a strange outlier and start with their graphics offset. Maximize the window after opening and it should be good.

While there is naitive support for per-window opacity via the `OPACITY` and `TRANSPARENTLIST` configuration macros, there is no support for per-pixel opacity. Programs that expect this behavior will render all pixels at the same opacity (unless using the `XSHAPE` extension for boolean opacity per-pixel (eg, `xeyes`), which works.)

## AUTHORS

- Derek Stevens <nilix@nilfm.cc>
- Russ Cox <rsc@swtch.com>
- David Hogan, RIP

## SEE ALSO

rio(1), 9term(1)