Configuration
Description
Define the behavior of Oxide. The config file provides the possibility to customize e. g. keybindings, layout, style. If the home config file is not existing, default values will be used but commands like exec and exec_always will not be working. The config file is written in YAML.
Files
During launch, Oxide searches for a config file in the following locations:
Home config file:
~/.config/Oxide/config.yml
System config file:
/etc/Oxide/config.yml
Keybindings
Keys
A keybinding has to consist of at least one or more MODIFIERS and exactly one normal key such as ‘t’ for example.
Modifier
Commands
Commands consist of a command and optional arguments.
Commands (COMMAND)
Arguments (ARGS)
Command arguments are necessary for the movement, the layout or to control workspaces.
Movement (MOVEMENT)
Layout (LAYOUT)
Workspace arguments (WORKSPACE_ARGS)
Iterations
The iteration commands provide the possibility to change between workspaces when given an iteration number as shown in the example down below.
Default keybindings
Here is a short overview of the default keybindings.
Borders
Execute
Examples
Keybindings
cmds:
- keys: ["M", "t"]
commands:
- command: Exec
args: "dmenu"
In this example pressing the meta key and ‘t’, a new dmenu window is opened.
Iterations
iter_cmds:
- iter: [1, 2, 3, 4, 5, 6, 7, 8, 9]
command:
keys: ["M", "C", "$VAR"]
commands:
- command: GoToWorkspace
args: "$VAR"
In this example using the ALT and CONTROL key paired with a number from one to nine, the user can go to the desired workspace.
$VAR
is a reference for the entered iterator.
Bugs
Please open an issue https://github.com/DHBW-FN/OxideWM/issues .