diff --git a/.github/actions/setup/action.yml b/.github/actions/setup/action.yml
index 639b22930..3ed378a5c 100644
--- a/.github/actions/setup/action.yml
+++ b/.github/actions/setup/action.yml
@@ -32,6 +32,7 @@ runs:
           libxkbcommon-dev \
           libxkbcommon-dev \
           libxkbcommon-x11-dev \
+          libgdk-pixbuf-2.0-dev \
           ninja-build \
           pandoc \
           python3-pip \
diff --git a/CONFIG.md b/CONFIG.md
index 44cf8f001..76007c824 100644
--- a/CONFIG.md
+++ b/CONFIG.md
@@ -20,7 +20,8 @@ configuration {
 
 }
 ```
-You can now set the options in the `configuration` block. 
+
+You can now set the options in the `configuration` block.
 
 ## Create a configuration file from current setup
 
@@ -35,6 +36,7 @@ This will have all the possible settings and their current value.
 If a value is the default value, the entry will be commented.
 
 For example:
+
 ```css
 configuration {               
 /*  modes: "window,run,ssh,drun";*/
@@ -68,8 +70,8 @@ newlines format are supported. But Unix is preferred.
 
 C and C++ file comments are supported.
 
-  - Anything after  `// ` and before a newline is considered a comment.
-  - Everything between `/*` and `*/` is a comment.
+- Anything after  `//` and before a newline is considered a comment.
+- Everything between `/*` and `*/` is a comment.
 
 Comments can be nested and the C comments can be inline.
 
@@ -124,12 +126,12 @@ For example:
 #### Number
 
 An integer may contain any full number.
-                                  
-For example:                     
-                                  
-```css                             
+
+For example:
+
+```css
 eh: 2;                        
-```                               
+```
 
 #### Boolean
 
@@ -144,15 +146,6 @@ show-icons: true;
 This is equal to the `-show-icons` option on the commandline, and `show-icons:
 false;` is equal to `-no-show-icons`.
 
-#### Character
-
-Character value is always surrounded by single quotes (') and should contain a
-single character. It supports escaping.
-
-```css
-matching-negate-char: '-';
-```
-
 #### List
 
 This is not supported by the old configuration system, but can be used in the
@@ -164,6 +157,7 @@ comma-separated. The entry in the list single ASCII words.
 ```css
  combi-modes: [window,drun];
 ```
+
 For older versions you have :
 
 ```css
diff --git a/COPYING b/COPYING
index 0bf135867..cd8c9adf3 100644
--- a/COPYING
+++ b/COPYING
@@ -1,5 +1,5 @@
 MIT/X11 License
-Modified  2013-2023 Qball Cow <qball@gmpclient.org>
+Modified  2013-2024 Qball Cow <qball@gmpclient.org>
 Copyright (c) 2012 Sean Pringle <sean.pringle@gmail.com>
 
 Permission is hereby granted, free of charge, to any person obtaining
diff --git a/Changelog b/Changelog
index 6a3e27145..f15123e64 100644
--- a/Changelog
+++ b/Changelog
@@ -1,3 +1,5 @@
+For newer release ChangeLogs please see the releasenotes.
+
 v1.7.3: Sturtled!
    - [Help] Print out the parsed config/theme files in -help output.
    - [Keybindings] Fix keybindings being modified by -theme-str
diff --git a/README.md b/README.md
index bc43c5a4f..592bbbeab 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@
 <h1 align="center"> Rofi </h1>
 <p align="center"><i>A window switcher, Application launcher and dmenu replacement</i>.</p>
 
-https://user-images.githubusercontent.com/84911063/139428874-fe182dd6-82c6-49b8-8da1-920ddda3d1ed.mp4
+<https://user-images.githubusercontent.com/84911063/139428874-fe182dd6-82c6-49b8-8da1-920ddda3d1ed.mp4>
 
 **This is a fork of [Rofi](https://github.com/davatorium/rofi) with added support for Wayland via the [layer shell protocol](https://github.com/swaywm/wlr-protocols).**
 **For more information, see the [Wayland support section](#wayland-support)**
@@ -33,15 +33,15 @@ provided by an external script.
 
 Rofi is not:
 
--   A UI toolkit.
+- A UI toolkit.
 
--   A library to be used in other applications.
+- A library to be used in other applications.
 
--   An application that can support every possible use-case. It tries to be
+- An application that can support every possible use-case. It tries to be
     generic enough to be usable by everybody.
-    - Specific functionality can be added using scripts or plugins, many exists.
+  - Specific functionality can be added using scripts or plugins, many exists.
 
--   Just a dmenu replacement. The dmenu functionality is a nice 'extra' to
+- Just a dmenu replacement. The dmenu functionality is a nice 'extra' to
     **rofi**, not its main purpose.
 
 ## Table of Contents
@@ -50,7 +50,7 @@ Rofi is not:
 - [Modes](#modes)
 - [Manpages](#manpage)
 - [Installation](#installation)
-- [Quickstart](#quickstart) 
+- [Quickstart](#quickstart)
   - [Usage](#usage)
   - [Configuration](#configuration)
   - [Themes](#themes)
@@ -61,47 +61,47 @@ Rofi is not:
 
 Its main features are:
 
--   Fully configurable keyboard navigation
+- Fully configurable keyboard navigation
 
--   Type to filter
-    - Tokenized: type any word in any order to filter
-    - Case insensitive (togglable)
-    - Support for fuzzy-, regex-, prefix-, and glob-matching
+- Type to filter
+  - Tokenized: type any word in any order to filter
+  - Case insensitive (togglable)
+  - Support for fuzzy-, regex-, prefix-, and glob-matching
 
--   UTF-8 enabled
-    - UTF-8-aware string collating
-    - International keyboard support (\`e -> è)
+- UTF-8 enabled
+  - UTF-8-aware string collating
+  - International keyboard support (\`e -> è)
 
--   RTL language support
+- RTL language support
 
--   Cairo drawing and Pango font rendering
+- Cairo drawing and Pango font rendering
 
--   Built-in modes:
-    -   Window switcher mode
-        - EWMH compatible WM
-        - Work arounds for i3,bspwm
+- Built-in modes:
+  - Window switcher mode
+    - EWMH compatible WM
+    - Work arounds for i3,bspwm
 
-    -   Application launcher
+  - Application launcher
 
-    -   Desktop file application launcher
+  - Desktop file application launcher
 
-    -   SSH launcher mode
+  - SSH launcher mode
 
-    -   File browser
+  - File browser
 
-    -   Combi mode, allowing several modes to be merged into one list
+  - Combi mode, allowing several modes to be merged into one list
 
--   History-based ordering — last 25 choices are ordered on top based on use
+- History-based ordering — last 25 choices are ordered on top based on use
     (optional)
 
--   Levenshtein distance or fzf like sorting of matches (optional)
+- Levenshtein distance or fzf like sorting of matches (optional)
 
--   Drop-in dmenu replacement
-    - Many added improvements
+- Drop-in dmenu replacement
+  - Many added improvements
 
--   Easily extensible using scripts and plugins
+- Easily extensible using scripts and plugins
 
--   Advanced Theming
+- Advanced Theming
 
 ## Modes
 
@@ -111,22 +111,22 @@ extended by scripts (either called from
 
 Below is a list of the different modes:
 
--   **run**: launch applications from $PATH, with option to launch in terminal.
+- **run**: launch applications from $PATH, with option to launch in terminal.
 
--   **drun**: launch applications based on desktop files. It tries to be
+- **drun**: launch applications based on desktop files. It tries to be
     compliant to the XDG standard.
 
--   **window**: Switch between windows on an EWMH compatible window manager.
+- **window**: Switch between windows on an EWMH compatible window manager.
 
--   **ssh**: Connect to a remote host via ssh.
+- **ssh**: Connect to a remote host via ssh.
 
--   **filebrowser**: A basic file-browser for opening files.
+- **filebrowser**: A basic file-browser for opening files.
 
--   **keys**: list internal keybindings.
+- **keys**: list internal keybindings.
 
--   **script**: Write (limited) custom mode using simple scripts.
+- **script**: Write (limited) custom mode using simple scripts.
 
--   **combi**: Combine multiple modes into one.
+- **combi**: Combine multiple modes into one.
 
 **Rofi** is known to work on Linux and BSD.
 
@@ -212,11 +212,11 @@ launcher:
 ```
 
 The modes to combine in combi mode.
-For syntax to `-combi-modes `, see `-modes`.
+For syntax to `-combi-modes`, see `-modes`.
 To get one merge view, of `window`,`run`, and `ssh`:
 
 ```bash
-	rofi -show combi -combi-modes "window,run,ssh" -modes combi
+ rofi -show combi -combi-modes "window,run,ssh" -modes combi
 ```
 
 ### Configuration
@@ -256,9 +256,9 @@ Default theme:
 
 ![default](https://raw.githubusercontent.com/davatorium/rofi/next/releasenotes/1.4.0/rofi-no-fzf.png)
 
-## Wiki 
+## Wiki
 
-| ❗ **The upstream rofi Wiki is currently unmaintained and might contain outdated data ** |
+| ❗ **The upstream rofi Wiki is currently unmaintained and might contain outdated data** |
 | --- |
 
 [Go to upstream rofi wiki](https://github.com/davatorium/rofi/wiki) .
diff --git a/configure.ac b/configure.ac
index efd630966..78a0cda28 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,4 +1,4 @@
-AC_INIT([rofi], [1.7.5-dev], [https://github.com/davatorium/rofi/],[],[https://github.com/davatorium/rofi/discussions])
+AC_INIT([rofi], [1.7.7], [https://github.com/davatorium/rofi/],[],[https://github.com/davatorium/rofi/discussions])
 
 AC_CONFIG_SRCDIR([source/rofi.c])
 AC_CONFIG_HEADER([config.h])
diff --git a/doc/rofi-keys.5.markdown b/doc/rofi-keys.5.markdown
index b6e264dfe..8aeefacc2 100644
--- a/doc/rofi-keys.5.markdown
+++ b/doc/rofi-keys.5.markdown
@@ -67,169 +67,169 @@ configuration {
 
 Paste primary selection
 
-Default: 	Control+V,Shift+Insert
+Default:  Control+V,Shift+Insert
 
 `kb-secondary-paste`
 
 Paste clipboard
 
-Default: 	Control+v,Insert
+Default:  Control+v,Insert
 
 `kb-secondary-copy`
 
 Copy current selection to clipboard
 
-Default: 	Control+c
+Default:  Control+c
 
 `kb-clear-line`
 
 Clear input line
 
-Default: 	Control+w
+Default:  Control+w
 
 `kb-move-front`
 
 Beginning of line
 
-Default: 	Control+a
+Default:  Control+a
 
 `kb-move-end`
 
 End of line
 
-Default: 	Control+e
+Default:  Control+e
 
 `kb-move-word-back`
 
 Move back one word
 
-Default: 	Alt+b,Control+Left
+Default:  Alt+b,Control+Left
 
 `kb-move-word-forward`
 
 Move forward one word
 
-Default: 	Alt+f,Control+Right
+Default:  Alt+f,Control+Right
 
 `kb-move-char-back`
 
 Move back one char
 
-Default: 	Left,Control+b
+Default:  Left,Control+b
 
 `kb-move-char-forward`
 
 Move forward one char
 
-Default: 	Right,Control+f
+Default:  Right,Control+f
 
 `kb-remove-word-back`
 
 Delete previous word
 
-Default: 	Control+Alt+h,Control+BackSpace
+Default:  Control+Alt+h,Control+BackSpace
 
 `kb-remove-word-forward`
 
 Delete next word
 
-Default: 	Control+Alt+d
+Default:  Control+Alt+d
 
 `kb-remove-char-forward`
 
 Delete next char
 
-Default: 	Delete,Control+d
+Default:  Delete,Control+d
 
 `kb-remove-char-back`
 
 Delete previous char
 
-Default: 	BackSpace,Shift+BackSpace,Control+h
+Default:  BackSpace,Shift+BackSpace,Control+h
 
 `kb-remove-to-eol`
 
 Delete till the end of line
 
-Default: 	Control+k
+Default:  Control+k
 
 `kb-remove-to-sol`
 
 Delete till the start of line
 
-Default: 	Control+u
+Default:  Control+u
 
 `kb-accept-entry`
 
 Accept entry
 
-Default: 	Control+j,Control+m,Return,KP\_Enter
+Default:  Control+j,Control+m,Return,KP\_Enter
 
 `kb-accept-custom`
 
 Use entered text as command (in ssh/run modes)
 
-Default: 	Control+Return
+Default:  Control+Return
 
 `kb-accept-custom-alt`
 
 Use entered text as command (in ssh/run modes)
 
-Default: 	Control+Shift+Return
+Default:  Control+Shift+Return
 
 `kb-accept-alt`
 
 Use alternate accept command.
 
-Default: 	Shift+Return
+Default:  Shift+Return
 
 `kb-delete-entry`
 
 Delete entry from history
 
-Default: 	Shift+Delete
+Default:  Shift+Delete
 
 `kb-mode-next`
 
 Switch to the next mode.
 
-Default: 	Shift+Right,Control+Tab
+Default:  Shift+Right,Control+Tab
 
 `kb-mode-previous`
 
 Switch to the previous mode.
 
-Default: 	Shift+Left,Control+ISO\_Left\_Tab
+Default:  Shift+Left,Control+ISO\_Left\_Tab
 
 `kb-mode-complete`
 
 Start completion for mode.
 
-Default: 	Control+l
+Default:  Control+l
 
 `kb-row-left`
 
 Go to the previous column
 
-Default: 	Control+Page\_Up
+Default:  Control+Page\_Up
 
 `kb-row-right`
 
 Go to the next column
 
-Default: 	Control+Page\_Down
+Default:  Control+Page\_Down
 
 `kb-row-up`
 
 Select previous entry
 
-Default: 	Up,Control+p
+Default:  Up,Control+p
 
 `kb-row-down`
 
 Select next entry
 
-Default: 	Down,Control+n
+Default:  Down,Control+n
 
 `kb-row-tab`
 
@@ -253,235 +253,235 @@ Default: ISO\_Left\_Tab
 
 Go to the previous page
 
-Default: 	Page\_Up
+Default:  Page\_Up
 
 `kb-page-next`
 
 Go to the next page
 
-Default: 	Page\_Down
+Default:  Page\_Down
 
 `kb-row-first`
 
 Go to the first entry
 
-Default: 	Home,KP\_Home
+Default:  Home,KP\_Home
 
 `kb-row-last`
 
 Go to the last entry
 
-Default: 	End,KP\_End
+Default:  End,KP\_End
 
 `kb-row-select`
 
 Set selected item as input text
 
-Default: 	Control+space
+Default:  Control+space
 
 `kb-screenshot`
 
 Take a screenshot of the rofi window
 
-Default: 	Alt+S
+Default:  Alt+S
 
 `kb-ellipsize`
 
 Toggle between ellipsize modes for displayed data
 
-Default: 	Alt+period
+Default:  Alt+period
 
 `kb-toggle-case-sensitivity`
 
 Toggle case sensitivity
 
-Default: 	grave,dead\_grave
+Default:  grave,dead\_grave
 
 `kb-toggle-sort`
 
 Toggle filtered menu sort
 
-Default: 	Alt+grave
+Default:  Alt+grave
 
 `kb-cancel`
 
 Quit rofi
 
-Default: 	Escape,Control+g,Control+bracketleft
+Default:  Escape,Control+g,Control+bracketleft
 
 `kb-custom-1`
 
 Custom keybinding 1
 
-Default: 	Alt+1
+Default:  Alt+1
 
 `kb-custom-2`
 
 Custom keybinding 2
 
-Default: 	Alt+2
+Default:  Alt+2
 
 `kb-custom-3`
 
 Custom keybinding 3
 
-Default: 	Alt+3
+Default:  Alt+3
 
 `kb-custom-4`
 
 Custom keybinding 4
 
-Default: 	Alt+4
+Default:  Alt+4
 
 `kb-custom-5`
 
 Custom Keybinding 5
 
-Default: 	Alt+5
+Default:  Alt+5
 
 `kb-custom-6`
 
 Custom keybinding 6
 
-Default: 	Alt+6
+Default:  Alt+6
 
 `kb-custom-7`
 
 Custom Keybinding 7
 
-Default: 	Alt+7
+Default:  Alt+7
 
 `kb-custom-8`
 
 Custom keybinding 8
 
-Default: 	Alt+8
+Default:  Alt+8
 
 `kb-custom-9`
 
 Custom keybinding 9
 
-Default: 	Alt+9
+Default:  Alt+9
 
 `kb-custom-10`
 
 Custom keybinding 10
 
-Default: 	Alt+0
+Default:  Alt+0
 
 `kb-custom-11`
 
 Custom keybinding 11
 
-Default: 	Alt+exclam
+Default:  Alt+exclam
 
 `kb-custom-12`
 
 Custom keybinding 12
 
-Default: 	Alt+at
+Default:  Alt+at
 
 `kb-custom-13`
 
 Custom keybinding 13
 
-Default: 	Alt+numbersign
+Default:  Alt+numbersign
 
 `kb-custom-14`
 
 Custom keybinding 14
 
-Default: 	Alt+dollar
+Default:  Alt+dollar
 
 `kb-custom-15`
 
 Custom keybinding 15
 
-Default: 	Alt+percent
+Default:  Alt+percent
 
 `kb-custom-16`
 
 Custom keybinding 16
 
-Default: 	Alt+dead\_circumflex
+Default:  Alt+dead\_circumflex
 
 `kb-custom-17`
 
 Custom keybinding 17
 
-Default: 	Alt+ampersand
+Default:  Alt+ampersand
 
 `kb-custom-18`
 
 Custom keybinding 18
 
-Default: 	Alt+asterisk
+Default:  Alt+asterisk
 
 `kb-custom-19`
 
 Custom Keybinding 19
 
-Default: 	Alt+parenleft
+Default:  Alt+parenleft
 
 `kb-select-1`
 
 Select row 1
 
-Default: 	Super+1
+Default:  Super+1
 
 `kb-select-2`
 
 Select row 2
 
-Default: 	Super+2
+Default:  Super+2
 
 `kb-select-3`
 
 Select row 3
 
-Default: 	Super+3
+Default:  Super+3
 
 `kb-select-4`
 
 Select row 4
 
-Default: 	Super+4
+Default:  Super+4
 
 `kb-select-5`
 
 Select row 5
 
-Default: 	Super+5
+Default:  Super+5
 
 `kb-select-6`
 
 Select row 6
 
-Default: 	Super+6
+Default:  Super+6
 
 `kb-select-7`
 
 Select row 7
 
-Default: 	Super+7
+Default:  Super+7
 
 `kb-select-8`
 
 Select row 8
 
-Default: 	Super+8
+Default:  Super+8
 
 `kb-select-9`
 
 Select row 9
 
-Default: 	Super+9
+Default:  Super+9
 
 `kb-select-10`
 
 Select row 10
 
-Default: 	Super+0
+Default:  Super+0
 
 `kb-entry-history-up`
 
@@ -501,43 +501,63 @@ Default:    Control+Down
 
 Go to the previous column
 
-Default: 	ScrollLeft
+Default:  ScrollLeft
 
 `ml-row-right`
 
 Go to the next column
 
-Default: 	ScrollRight
+Default:  ScrollRight
 
 `ml-row-up`
 
 Select previous entry
 
-Default: 	ScrollUp
+Default:  ScrollUp
 
 `ml-row-down`
 
 Select next entry
 
-Default: 	ScrollDown
+Default:  ScrollDown
 
 `me-select-entry`
 
 Select hovered row
 
-Default: 	MousePrimary
+Default:  MousePrimary
 
 `me-accept-entry`
 
 Accept hovered row
 
-Default: 	MouseDPrimary
+Default:  MouseDPrimary
 
 `me-accept-custom`
 
 Accept hovered row with custom action
 
-Default: 	Control+MouseDPrimary
+Default:  Control+MouseDPrimary
+
+## Mouse key bindings
+
+The following mouse buttons can be bound:
+
+* `Primary`: Primary (Left) mouse button click.
+* `Secondary`:  Secondary (Right) mouse button click.
+* `Middle`: Middle mouse button click.
+* `Forward`: The forward mouse button.
+* `Back`: The back mouse button.
+* `ExtraN`: The N'the mouse button. (Depending on mouse support).
+
+The Identifier is constructed as follow:
+
+`Mouse<D><Button>`
+
+* `D` indicates optional Double press.
+* `Button` is the button name.
+
+So `MouseDPrimary` is Primary (`Left`) mouse button double click.
 
 ## SEE ALSO
 
diff --git a/doc/rofi-theme.5.markdown b/doc/rofi-theme.5.markdown
index 90a273f19..dd6c2b4f1 100644
--- a/doc/rofi-theme.5.markdown
+++ b/doc/rofi-theme.5.markdown
@@ -195,9 +195,9 @@ newlines format are supported. But unix is preferred.
 
 C and C++ file comments are supported.
 
--   Anything after  `// ` and before a newline is considered a comment.
+- Anything after  `//` and before a newline is considered a comment.
 
--   Everything between `/*` and `*/` is a comment, this comment can span
+- Everything between `/*` and `*/` is a comment, this comment can span
     multiple lines.
 
 Comments can be nested and the C comments can be inline.
@@ -443,17 +443,17 @@ dynamic: false;
 
 **rofi** support a limited set of background-image formats.
 
--   Format: url("path to image");
+- Format: url("path to image");
 
--   Format: url("path to image", scale);
+- Format: url("path to image", scale);
     where scale is: none, both, width, height
 
--   Format: linear-gradient(stop color,stop1, color, stop2 color, ...);
+- Format: linear-gradient(stop color,stop1, color, stop2 color, ...);
 
--   Format: linear-gradient(to direction, stop color,stop1, color, stop2 color,
+- Format: linear-gradient(to direction, stop color,stop1, color, stop2 color,
     ...); where direction is:   top,left,right,bottom.
 
--   Format: linear-gradient(angle, stop color,stop1, color, stop2 color, ...);
+- Format: linear-gradient(angle, stop color,stop1, color, stop2 color, ...);
     Angle in deg,rad,grad (as used in color).
 
 Where the `path` is a string, and `stop` color is of type color.
@@ -463,42 +463,42 @@ Where the `path` is a string, and `stop` color is of type color.
 **rofi** supports the color formats as specified in the CSS standard (1,2,3 and
 some of CSS 4)
 
--   Format: `#{HEX}{3}` (rgb)
+- Format: `#{HEX}{3}` (rgb)
 
--   Format: `#{HEX}{4}` (rgba)
+- Format: `#{HEX}{4}` (rgba)
 
--   Format: `#{HEX}{6}` (rrggbb)
+- Format: `#{HEX}{6}` (rrggbb)
 
--   Format: `#{HEX}{8}` (rrggbbaa)
+- Format: `#{HEX}{8}` (rrggbbaa)
 
--   Format: `rgb[a]({INTEGER},{INTEGER},{INTEGER}[, {PERCENTAGE}])`
+- Format: `rgb[a]({INTEGER},{INTEGER},{INTEGER}[, {PERCENTAGE}])`
 
--   Format: `rgb[a]({INTEGER}%,{INTEGER}%,{INTEGER}%[, {PERCENTAGE}])`
+- Format: `rgb[a]({INTEGER}%,{INTEGER}%,{INTEGER}%[, {PERCENTAGE}])`
 
--   Format: `hsl[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
+- Format: `hsl[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
 
--   Format: `hwb[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
+- Format: `hwb[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
 
--   Format: `cmyk( {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE} [,
+- Format: `cmyk( {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE} [,
     {PERCENTAGE} ])`
 
--   Format: `{named-color} [ / {PERCENTAGE} ]`
+- Format: `{named-color} [ / {PERCENTAGE} ]`
 
 The white-space format proposed in CSS4 is also supported.
 
 The different values are:
 
--   `{HEX}` is a hexadecimal number ('0-9a-f' case insensitive).
+- `{HEX}` is a hexadecimal number ('0-9a-f' case insensitive).
 
--   `{INTEGER}` value can be between 0 and 255 or 0-100 when representing
+- `{INTEGER}` value can be between 0 and 255 or 0-100 when representing
     percentage.
 
--   `{ANGLE}` is the angle on the color wheel, can be in `deg`, `rad`, `grad`
+- `{ANGLE}` is the angle on the color wheel, can be in `deg`, `rad`, `grad`
     or `turn`. When no unit is specified, degrees is assumed.
 
--   `{PERCENTAGE}` can be between 0-1.0, or 0%-100%
+- `{PERCENTAGE}` can be between 0-1.0, or 0%-100%
 
--   `{named-color}` is one of the following colors:
+- `{named-color}` is one of the following colors:
 
     AliceBlue, AntiqueWhite, Aqua, Aquamarine, Azure, Beige, Bisque, Black,
     BlanchedAlmond, Blue, BlueViolet, Brown, BurlyWood, CadetBlue, Chartreuse,
@@ -532,6 +532,7 @@ background-color: #FF0000;
 border-color: rgba(0,0,1, 0.5);
 text-color: SeaGreen;
 ```
+
 or
 
 ```css
@@ -567,6 +568,7 @@ upsizing or wrapping. This will be re-enabled once fixed:
 
 Indicates how a line should be drawn.
 It currently supports:
+
 - `dash`:  a dashed line, where the gap is the same width as the dash
 - `solid`: a solid line
 
@@ -593,6 +595,7 @@ For example:
 ```css
    padding: 10%;
 ```
+
 On a full-HD (1920x1080) monitor, it defines a padding of 192 pixels on the left
 and right side and 108 pixels on the top and bottom.
 
@@ -617,9 +620,9 @@ It supports the following operations:
 - `modulo` : Modulo
 - `min`    : Minimum of lvalue or rvalue;
 - `max`    : Maximum of lvalue or rvalue;
-- `floor`  : Round down lvalue to the next multiple of rvalue 
-- `ceil`   : Round up lvalue to the next multiple of rvalue 
-- `round`  : Round lvalue to the next multiple of rvalue 
+- `floor`  : Round down lvalue to the next multiple of rvalue
+- `ceil`   : Round up lvalue to the next multiple of rvalue
+- `round`  : Round lvalue to the next multiple of rvalue
 
 It uses the C precedence ordering.
 
@@ -642,24 +645,24 @@ The different number of fields in the formats are parsed like:
 
 ### Border
 
--   Format: `{Integer}`
+- Format: `{Integer}`
 
--   Format: `{Distance}`
+- Format: `{Distance}`
 
--   Format: `{Distance} {Distance}`
+- Format: `{Distance} {Distance}`
 
--   Format: `{Distance} {Distance} {Distance}`
+- Format: `{Distance} {Distance} {Distance}`
 
--   Format: `{Distance} {Distance} {Distance} {Distance}`
+- Format: `{Distance} {Distance} {Distance} {Distance}`
 
--   Format: `{Distance} {Line style}`
+- Format: `{Distance} {Line style}`
 
--   Format: `{Distance} {Line style} {Distance} {Line style}`
+- Format: `{Distance} {Line style} {Distance} {Line style}`
 
--   Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
+- Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
     style}`
 
--   Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
+- Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
     style} {Distance} {Line style}`
 
 Borders are identical to padding, except that each distance field has a line
@@ -838,50 +841,50 @@ element selected {
 The default widgets available in **rofi** and the default hierarchic:
 
 - `window`
-  -   `overlay`: the overlay widget.
+  - `overlay`: the overlay widget.
 
-  -   `mainbox`: The mainbox box.
+  - `mainbox`: The mainbox box.
 
-   -   `inputbar`: The input bar box.
-       -   `box`: the horizontal @box packing the widgets
+  - `inputbar`: The input bar box.
+    - `box`: the horizontal @box packing the widgets
 
-          -   `case-indicator`: the case/sort indicator @textbox
+    - `case-indicator`: the case/sort indicator @textbox
 
-          -   `prompt`: the prompt @textbox
+    - `prompt`: the prompt @textbox
 
-          -   `entry`: the main entry @textbox
+    - `entry`: the main entry @textbox
 
-          -   `num-rows`: Shows the total number of rows.
+    - `num-rows`: Shows the total number of rows.
 
-          -   `num-filtered-rows`: Shows the total number of rows after
+    - `num-filtered-rows`: Shows the total number of rows after
               filtering.
 
-          -   `textbox-current-entry`: Shows the text of the currently selected
+    - `textbox-current-entry`: Shows the text of the currently selected
               entry.
 
-          -   `icon-current-entry`: Shows the icon of the currently selected
+    - `icon-current-entry`: Shows the icon of the currently selected
               entry.
 
-   -   `listview`: The listview.
+  - `listview`: The listview.
 
-       -   `scrollbar`: the listview scrollbar
+    - `scrollbar`: the listview scrollbar
 
-       -   `element`: a box in the listview holding the entries
+    - `element`: a box in the listview holding the entries
 
-	     -   `element-icon`: the widget in the listview's entry showing the
-		 (optional) icon
+      - `element-icon`: the widget in the listview's entry showing the
+   (optional) icon
 
-	     -   `element-index`: the widget in the listview's entry
-		 keybindable index (1,2,3..0)
+      - `element-index`: the widget in the listview's entry
+   keybindable index (1,2,3..0)
 
-	     -   `element-text`: the widget in the listview's entry showing the
-		 text.
+      - `element-text`: the widget in the listview's entry showing the
+   text.
 
-   -   `mode-switcher`: the main horizontal @box packing the buttons.
-       - `button`: the buttons @textbox for each mode
+  - `mode-switcher`: the main horizontal @box packing the buttons.
+    - `button`: the buttons @textbox for each mode
 
-   -   `message`: The container holding the textbox.
-       - `textbox`: the message textbox
+  - `message`: The container holding the textbox.
+    - `textbox`: the message textbox
 
 Note that these path names match the default theme. Themes that provide a
 custom layout will have different elements, and structure.
@@ -911,11 +914,13 @@ Currently only the entrybox and scrollbar have states:
 ```
 
 Where `visible modifier` can be:
+
 - normal: no modification
 - selected: the entry is selected/highlighted by user
 - alternate: the entry is at an alternating row (uneven row)
 
 Where `state` is:
+
 - normal: no modification
 - urgent: this entry is marked urgent
 - active: this entry is marked active
@@ -944,60 +949,60 @@ This allows the colors used for drawing the handle to be set independently.
 
 The following properties are currently supported:
 
-###  all widgets
+### all widgets
 
--   **enabled**:           enable/disable rendering of the widget
+- **enabled**:           enable/disable rendering of the widget
 
--   **padding**:           padding
+- **padding**:           padding
     Padding on the inside of the widget
 
--   **margin**:            padding
+- **margin**:            padding
     Margin on the outside of the widget
 
--   **border**:            border
+- **border**:            border
     Border around the widget (between padding and margin)/
 
--   **border-radius**:     padding
+- **border-radius**:     padding
     Sets a radius on the corners of the borders.
 
--   **background-color**:  color
+- **background-color**:  color
     Background color
 
--   **background-image**:  image
+- **background-image**:  image
     Background image
 
--   **border-color**:      color
+- **border-color**:      color
     Color of the border
 
--   **cursor**:            cursor
+- **cursor**:            cursor
     Type of mouse cursor that is set when the mouse pointer is hovered over the
     widget.
 
 ### window
 
--   **font**:            string
+- **font**:            string
     The font used in the window
 
--   **transparency**:    string
+- **transparency**:    string
     Indicating if transparency should be used and what type:
-    - **real** - True transparency. Only works with a compositor.
-    - **background** - Take a screenshot of the background image and use that.
-    - **screenshot** - Take a screenshot of the screen and use that.
-    - **Path** to png file - Use an image.
+  - **real** - True transparency. Only works with a compositor.
+  - **background** - Take a screenshot of the background image and use that.
+  - **screenshot** - Take a screenshot of the screen and use that.
+  - **Path** to png file - Use an image.
 
--   **location**:       position
+- **location**:       position
       The place of the anchor on the monitor
 
--   **anchor**:         anchor
+- **anchor**:         anchor
       The anchor position on the window
 
--   **fullscreen**:     boolean Window is fullscreen.
+- **fullscreen**:     boolean Window is fullscreen.
 
--   **width**:          distance The width of the window
+- **width**:          distance The width of the window
 
--   **x-offset**:       distance
+- **x-offset**:       distance
 
--   **y-offset**:       distance The offset of the window to the anchor point,
+- **y-offset**:       distance The offset of the window to the anchor point,
     allowing you to push the window left/right/up/down
 
 ### scrollbar Properties
@@ -1014,102 +1019,103 @@ The following properties are currently supported:
 
 ### textbox
 
--   **background-color**:  color
+- **background-color**:  color
 
--   **border-color**:      the color used for the border around the widget.
+- **border-color**:      the color used for the border around the widget.
 
--   **font**:              the font used by this textbox (string).
+- **font**:              the font used by this textbox (string).
 
--   **str**/**content**:   the string to display by this textbox (string).
+- **str**/**content**:   the string to display by this textbox (string).
 
--   **vertical-align**:    Vertical alignment of the text. A number between 0
+- **vertical-align**:    Vertical alignment of the text. A number between 0
     (top) and 1 (bottom).
 
--   **horizontal-align**:  Horizontal alignment of the text. A number between 0
+- **horizontal-align**:  Horizontal alignment of the text. A number between 0
     (left) and 1 (right).
 
--   **text-color**:        the text color to use.
+- **text-color**:        the text color to use.
 
--   **text-transform**:    text style {color} for the whole text.
+- **text-transform**:    text style {color} for the whole text.
 
--   **highlight**:         text style {color}. color is optional, multiple
+- **highlight**:         text style {color}. color is optional, multiple
     highlight styles can be added like: bold underline italic #000000; This
     option is only available on the `element-text` widget.
 
--   **width**:             override the desired width for the textbox.
+- **width**:             override the desired width for the textbox.
 
--   **content**:           Set the displayed text (String).
+- **content**:           Set the displayed text (String).
 
--   **placeholder**:       Set the displayed text (String) when nothing is
+- **placeholder**:       Set the displayed text (String) when nothing is
     entered.
 
--   **placeholder-markup**:       If true, placeholder text supports pango
+- **placeholder-markup**:       If true, placeholder text supports pango
     markup for stylizing.
 
--   **placeholder-color**: Color of the placeholder text.
+- **placeholder-color**: Color of the placeholder text.
 
--   **blink**:             Enable/Disable blinking on an input textbox
+- **blink**:             Enable/Disable blinking on an input textbox
     (Boolean).
 
--   **markup**:            Force markup on, beware that only valid pango markup
+- **markup**:            Force markup on, beware that only valid pango markup
     strings are shown.
 
--   **tab-stops**:         array of distances. Set the location of tab stops by
+- **tab-stops**:         array of distances. Set the location of tab stops by
     their distance from the beginning of the line. Each distance should be
     greater than the previous one. The text appears to the right of the tab
     stop position (other alignments are not supported yet).
 
--   **cursor-width**:      The width of the cursor.
+- **cursor-width**:      The width of the cursor.
 
--   **cursor-color**:      The color used to draw the cursor.
+- **cursor-color**:      The color used to draw the cursor.
 
--   **cursor-outline**:      Enable a border (outline) around the cursor.
+- **cursor-outline**:      Enable a border (outline) around the cursor.
     (Boolean)
 
--   **cursor-outline-width**: The width of the border around the cursor.
+- **cursor-outline-width**: The width of the border around the cursor.
     (Double)
 
--   **cursor-outline-color**: The color to use for the cursor outline.
+- **cursor-outline-color**: The color to use for the cursor outline.
     (Color)
 
--   **text-outline**:      Enable a border (outline) around the text. (Boolean)
+- **text-outline**:      Enable a border (outline) around the text. (Boolean)
 
--   **text-outline-width**: The width of the border around the text.  (Double)
+- **text-outline-width**: The width of the border around the text.  (Double)
 
--   **text-outline-color**: The color to use for the text outline.    (Color)
+- **text-outline-color**: The color to use for the text outline.    (Color)
 
 ### listview
--   **columns**:         integer Number of columns to show (at least 1)
 
--   **fixed-height**:    boolean Always show `lines` rows, even if fewer
+- **columns**:         integer Number of columns to show (at least 1)
+
+- **fixed-height**:    boolean Always show `lines` rows, even if fewer
     elements are available.
 
--   **dynamic**:         boolean `True` if the size should change when filtering
+- **dynamic**:         boolean `True` if the size should change when filtering
     the list, `False` if it should keep the original height.
 
--   **scrollbar**:       boolean If the scrollbar should be enabled/disabled.
+- **scrollbar**:       boolean If the scrollbar should be enabled/disabled.
 
--   **scrollbar-width**: distance Width of the scrollbar
+- **scrollbar-width**: distance Width of the scrollbar
 
--   **cycle**:           boolean When navigating, it should wrap around
+- **cycle**:           boolean When navigating, it should wrap around
 
--   **spacing**:         distance Spacing between the elements (both vertical
+- **spacing**:         distance Spacing between the elements (both vertical
     and horizontal)
 
--   **lines**:           integer Number of rows to show in the list view.
+- **lines**:           integer Number of rows to show in the list view.
 
--   **layout**:           orientation Indicate how elements are stacked.
+- **layout**:           orientation Indicate how elements are stacked.
     Horizontal implements the dmenu style.
 
--   **reverse**:         boolean Reverse the ordering (top down to bottom up).
+- **reverse**:         boolean Reverse the ordering (top down to bottom up).
 
--   **flow**:           orientation The order the elements are layed out.
+- **flow**:           orientation The order the elements are layed out.
     Vertical is the original 'column' view.
 
--   **fixed-columns**:    boolean Do not reduce the number of columns shown when
+- **fixed-columns**:    boolean Do not reduce the number of columns shown when
     number of visible elements is not enough to fill them all.
 
--   **require-input**:    boolean Listview requires user input to be unhidden.
+- **require-input**:    boolean Listview requires user input to be unhidden.
     The list is still present and hitting accept will activate the first entry.
 
 ## Listview widget
@@ -1117,9 +1123,9 @@ The following properties are currently supported:
 The listview widget is special container widget.
 It has the following fixed children widgets:
 
--   0 or more `element` widgets of the type box.
+- 0 or more `element` widgets of the type box.
 
--   An optional `scrollbar` widget. This can be enabled using the scrollbar
+- An optional `scrollbar` widget. This can be enabled using the scrollbar
     property.
 
 These cannot be changed using the `children` property.
@@ -1215,6 +1221,7 @@ The current layout of **rofi** is structured as follows:
 
 
 ```
+>
 > - ci is the case-indicator
 > - fr is the num-filtered-rows
 > - ns is the num-rows
@@ -1390,15 +1397,15 @@ Just like CSS, **rofi** uses the box model for each widget.
 
 Explanation of the different parts:
 
--   Content - The content of the widget.
+- Content - The content of the widget.
 
--   Padding - Clears an area around the widget. The padding shows the
+- Padding - Clears an area around the widget. The padding shows the
     background color of the widget.
 
--   Border - A border that goes around the padding and content. The border use
+- Border - A border that goes around the padding and content. The border use
     the border-color of the widget.
 
--   Margin - Clears an area outside the border. The margin is transparent.
+- Margin - Clears an area outside the border. The margin is transparent.
 
 The box model allows us to add a border around elements, and to define space
 between elements.
@@ -1594,7 +1601,7 @@ A typical example:
 
 "Cantarell Italic Light 15 \`wght`=200"
 
-## Icon Handling 
+## Icon Handling
 
 Rofi supports 3 ways of specifying an icon:
 
@@ -1618,6 +1625,7 @@ Getting supported icon formats:
 ```bash
 G_MESSAGES_DEBUG=Helpers.IconFetcher rofi
 ```
+
 This uses the debug framework and prints out a list of supported image  file
 extensions.
 
@@ -1647,7 +1655,8 @@ If a filename is provided, it will try to resolve it in the following order:
 - `${XDG_DATA_HOME}/rofi/themes/`
 - `${INSTALL PREFIX}/share/rofi/themes/`
 
-A name is resolved (if it has no valid extension) as a filename by appending the `.rasi` extension.
+A name is resolved (if it has no valid extension) as a filename by appending the `.rasi` and the `.rasinc` extension.
+It will first look for files with `.rasi`, then for files with `.rasinc`.
 
 ## Examples
 
diff --git a/doc/rofi.1.markdown b/doc/rofi.1.markdown
index 3c5a6afe0..20cdd721c 100644
--- a/doc/rofi.1.markdown
+++ b/doc/rofi.1.markdown
@@ -66,15 +66,15 @@ Markup support can be enabled, see CONFIGURATION options.
 There are currently three methods of setting configuration options (evaluated
 in order below):
 
--   System configuration file  (for example `/etc/rofi.rasi`). It first checks
+- System configuration file  (for example `/etc/rofi.rasi`). It first checks
     `XDG_CONFIG_DIRS`, and then `SYSCONFDIR` (that is passed at compile time).
     It loads the first config file it finds, it does not merge multiple system
     configuration files.
 
--   Rasi theme file: The new *theme* format can be used to set configuration
+- Rasi theme file: The new *theme* format can be used to set configuration
     values.
 
--   Command-line options: Arguments passed to **rofi**.
+- Command-line options: Arguments passed to **rofi**.
 
 To get a template config file, run: `rofi -dump-config > config.rasi`
 
@@ -102,7 +102,7 @@ For example to set the dpi value to 72:
 
 ```css
 configuration {
-	dpi: 72;
+ dpi: 72;
 }
 ```
 
@@ -329,6 +329,7 @@ configuration {
     }
 }
 ```
+
 Example
 
 ```css
@@ -423,10 +424,10 @@ For Wayland, the list of accepted fields is different:
 
 Default: *all*
 
-`-matching-negate-char` *char*
+`-matching-negate-char` *string*
 
 Set the character used to negate the query (i.e. if it does **not** match the
-next keyword). Set to '\x0' to disable.
+next keyword). Set to '\x0' to disable. It takes the first ASCII character from the string.
 
 Default: '-'
 
@@ -473,7 +474,7 @@ Default: *0*
 
 `-fixed-num-lines`
 
-Keep a fixed number of visible lines. 
+Keep a fixed number of visible lines.
 
 `-sidebar-mode`
 
@@ -509,17 +510,17 @@ Select monitor to display **rofi** on. It accepts as input: *primary* (if
 primary output is set), the *xrandr* output name, or integer number (in order
 of detection). Negative numbers are handled differently:
 
--   **-1**: the currently focused monitor.
+- **-1**: the currently focused monitor.
 
--   **-2**: the currently focused window (that is, **rofi** will be displayed
+- **-2**: the currently focused window (that is, **rofi** will be displayed
     on top of the focused window).
 
--   **-3**: Position of mouse (overrides the location setting to get normal
+- **-3**: Position of mouse (overrides the location setting to get normal
     context menu behavior.)
 
--   **-4**: the monitor with the focused window.
+- **-4**: the monitor with the focused window.
 
--   **-5**: the monitor that shows the mouse pointer.
+- **-5**: the monitor that shows the mouse pointer.
 
 Default: *-5*
 
@@ -546,10 +547,10 @@ This is now the method to tweak the theme via the command line.
 
 Override the default DPI setting.
 
--   If set to `0`, it tries to auto-detect based on X11 screen size (similar to
+- If set to `0`, it tries to auto-detect based on X11 screen size (similar to
     i3 and GTK).
 
--   If set to `1`, it tries to auto-detect based on the size of the monitor
+- If set to `1`, it tries to auto-detect based on the size of the monitor
     that **rofi** is displayed on (similar to latest Qt 5).
 
 `-selected-row` *selected row*
@@ -676,6 +677,7 @@ configuration {
   }
 }
 ```
+
 You can hide the currently active window with the 'hide-active-window' setting:
 
 ```css
@@ -703,7 +705,7 @@ or pass `-window-prefer-icon-theme true` on command line.
 
 ### Combi settings
 
-`-combi-modes ` *mode1*,*mode2*
+`-combi-modes` *mode1*,*mode2*
 
 The modes to combine in combi mode.
 For syntax to `-combi-modes`, see `-modes`.
@@ -965,13 +967,13 @@ If there is no match, it will try to launch the input.
 Shows a list of executables in `$PATH` and can launch them (optional in a
 terminal).
 
--   Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
+- Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
     from the run history.
 
--   Pressing the `accept-custom` binding (`control-enter`) will run the command
+- Pressing the `accept-custom` binding (`control-enter`) will run the command
     as entered in the entry box.
 
--   Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
+- Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
     terminal.
 
 When pressing the `mode-complete` binding (`Control-l`), you can use the File
@@ -983,13 +985,13 @@ Same as the **run** launches, but the list is created from the installed
 desktop files. It automatically launches them in a terminal if specified in the
 Desktop File.
 
--   Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
+- Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
     from the run history.
 
--   Pressing the `accept-custom` binding (`control-enter`) will run the command
+- Pressing the `accept-custom` binding (`control-enter`) will run the command
     as entered in the entry box.
 
--   Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
+- Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
     terminal.
 
 When pressing the `mode-complete` binding (`Control-l`), you can use the File
@@ -1017,6 +1019,7 @@ configuration {
    }
 }
 ```
+
 ### ssh
 
 Shows a list of SSH targets based on your `ssh` config file, and allows to
@@ -1059,7 +1062,7 @@ instead of `"` ("machine quotes").
 
 The indicator shows:
 
-- ` ` Case insensitive and no sorting.
+- `` Case insensitive and no sorting.
 - `-` Case sensitivity enabled, no sorting.
 - `+` Case insensitive and Sorting enabled
 - `±` Sorting and Case sensitivity enabled"
@@ -1068,13 +1071,13 @@ The indicator shows:
 
 Each of these modes uses different methods of resolving the icon:
 
--   Window: It first uses the icon that the application exposes via the X11
+- Window: It first uses the icon that the application exposes via the X11
     Server, if none is set it does a lookup of the window Class name in the icon
     theme.
 
--   drun: It uses the icon set in the desktop file.
+- drun: It uses the icon set in the desktop file.
 
--   run: It does a lookup using the executable name.
+- run: It does a lookup using the executable name.
 
 ## EXAMPLES
 
@@ -1172,7 +1175,7 @@ after the keys have been released.
 
 ## DEBUGGING
 
-For more information see **rofi-debugging(5)** manpage. 
+For more information see **rofi-debugging(5)** manpage.
 
 ## ISSUE TRACKER
 
diff --git a/doc/rofi.doxy.in b/doc/rofi.doxy.in
index b3ffb8ece..b91a6300c 100644
--- a/doc/rofi.doxy.in
+++ b/doc/rofi.doxy.in
@@ -1,7 +1,7 @@
-# Doxyfile 1.8.9.1
+# Doxyfile 1.12.0
 
 # This file describes the settings to be used by the documentation system
-# doxygen (www.doxygen.org) for a project.
+# Doxygen (www.doxygen.org) for a project.
 #
 # All text after a double hash (##) is considered a comment and is placed in
 # front of the TAG it is preceding.
@@ -12,16 +12,26 @@
 # For lists, items can also be appended using:
 # TAG += value [value, ...]
 # Values that contain spaces should be placed between quotes (\" \").
+#
+# Note:
+#
+# Use Doxygen to compare the used configuration file with the template
+# configuration file:
+# doxygen -x [configFile]
+# Use Doxygen to compare the used configuration file with the template
+# configuration file without replacing the environment variables or CMake type
+# replacement variables:
+# doxygen -x_noenv [configFile]
 
 #---------------------------------------------------------------------------
 # Project related configuration options
 #---------------------------------------------------------------------------
 
-# This tag specifies the encoding used for all characters in the config file
-# that follow. The default is UTF-8 which is also the encoding used for all text
-# before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
-# built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
-# for the list of possible encodings.
+# This tag specifies the encoding used for all characters in the configuration
+# file that follow. The default is UTF-8 which is also the encoding used for all
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the
+# iconv built into libc) for the transcoding. See
+# https://www.gnu.org/software/libiconv/ for the list of possible encodings.
 # The default value is: UTF-8.
 
 DOXYFILE_ENCODING      = UTF-8
@@ -32,13 +42,13 @@ DOXYFILE_ENCODING      = UTF-8
 # title of most generated pages and in a few other places.
 # The default value is: My Project.
 
-PROJECT_NAME           = "@PACKAGE@"
+PROJECT_NAME           = @PACKAGE@
 
 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = "@VERSION@"
+PROJECT_NUMBER         = @VERSION@
 
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a
@@ -53,46 +63,67 @@ PROJECT_BRIEF          =
 
 PROJECT_LOGO           =
 
+
 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
 # into which the generated documentation will be written. If a relative path is
-# entered, it will be relative to the location where doxygen was started. If
+# entered, it will be relative to the location where Doxygen was started. If
 # left blank the current directory will be used.
 
 OUTPUT_DIRECTORY       = @abs_builddir@/html/
 
-# If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
-# directories (in 2 levels) under the output directory of each output format and
-# will distribute the generated files over these directories. Enabling this
-# option can be useful when feeding doxygen a huge amount of source files, where
+# If the CREATE_SUBDIRS tag is set to YES then Doxygen will create up to 4096
+# sub-directories (in 2 levels) under the output directory of each output format
+# and will distribute the generated files over these directories. Enabling this
+# option can be useful when feeding Doxygen a huge amount of source files, where
 # putting all generated files in the same directory would otherwise causes
-# performance problems for the file system.
+# performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to
+# control the number of sub-directories.
 # The default value is: NO.
 
 CREATE_SUBDIRS         = NO
 
+# Controls the number of sub-directories that will be created when
+# CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every
+# level increment doubles the number of directories, resulting in 4096
+# directories at level 8 which is the default and also the maximum value. The
+# sub-directories are organized in 2 levels, the first level always has a fixed
+# number of 16 directories.
+# Minimum value: 0, maximum value: 8, default value: 8.
+# This tag requires that the tag CREATE_SUBDIRS is set to YES.
+
+CREATE_SUBDIRS_LEVEL   = 8
+
+# If the ALLOW_UNICODE_NAMES tag is set to YES, Doxygen will allow non-ASCII
+# characters to appear in the names of generated files. If set to NO, non-ASCII
+# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
+# U+3044.
+# The default value is: NO.
+
+ALLOW_UNICODE_NAMES    = NO
+
 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
-# documentation generated by doxygen is written. Doxygen will use this
+# documentation generated by Doxygen is written. Doxygen will use this
 # information to generate all constant output in the proper language.
-# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
-# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
-# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
-# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
-# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
-# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
-# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
-# Ukrainian and Vietnamese.
+# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian,
+# Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English
+# (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek,
+# Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with
+# English messages), Korean, Korean-en (Korean with English messages), Latvian,
+# Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese,
+# Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish,
+# Swedish, Turkish, Ukrainian and Vietnamese.
 # The default value is: English.
 
 OUTPUT_LANGUAGE        = English
 
-# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
+# If the BRIEF_MEMBER_DESC tag is set to YES, Doxygen will include brief member
 # descriptions after the members that are listed in the file and class
 # documentation (similar to Javadoc). Set to NO to disable this.
 # The default value is: YES.
 
 BRIEF_MEMBER_DESC      = YES
 
-# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
+# If the REPEAT_BRIEF tag is set to YES, Doxygen will prepend the brief
 # description of a member or function before the detailed description
 #
 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
@@ -110,9 +141,9 @@ REPEAT_BRIEF           = YES
 # the entity):The $name class, The $name widget, The $name file, is, provides,
 # specifies, contains, represents, a, an and the.
 
-ABBREVIATE_BRIEF       = "The $name class " \
-                         "The $name widget " \
-                         "The $name file " \
+ABBREVIATE_BRIEF       = "The $name class" \
+                         "The $name widget" \
+                         "The $name file" \
                          is \
                          provides \
                          specifies \
@@ -123,13 +154,13 @@ ABBREVIATE_BRIEF       = "The $name class " \
                          the
 
 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
-# doxygen will generate a detailed section even if there is only a brief
+# Doxygen will generate a detailed section even if there is only a brief
 # description.
 # The default value is: NO.
 
 ALWAYS_DETAILED_SEC    = NO
 
-# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
+# If the INLINE_INHERITED_MEMB tag is set to YES, Doxygen will show all
 # inherited members of a class in the documentation of that class as if those
 # members were ordinary class members. Constructors, destructors and assignment
 # operators of the base classes will not be shown.
@@ -137,7 +168,7 @@ ALWAYS_DETAILED_SEC    = NO
 
 INLINE_INHERITED_MEMB  = NO
 
-# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
+# If the FULL_PATH_NAMES tag is set to YES, Doxygen will prepend the full path
 # before files name in the file list and in the header files. If set to NO the
 # shortest path that makes the file name unique will be used
 # The default value is: YES.
@@ -147,11 +178,11 @@ FULL_PATH_NAMES        = YES
 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
 # Stripping is only done if one of the specified strings matches the left-hand
 # part of the path. The tag can be used to show relative paths in the file list.
-# If left blank the directory from which doxygen is run is used as the path to
+# If left blank the directory from which Doxygen is run is used as the path to
 # strip.
 #
 # Note that you can specify absolute paths here, but also relative paths, which
-# will be relative from the directory where doxygen is started.
+# will be relative from the directory where Doxygen is started.
 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
 
 STRIP_FROM_PATH        =
@@ -165,14 +196,14 @@ STRIP_FROM_PATH        =
 
 STRIP_FROM_INC_PATH    =
 
-# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
+# If the SHORT_NAMES tag is set to YES, Doxygen will generate much shorter (but
 # less readable) file names. This can be useful is your file systems doesn't
 # support long names like on DOS, Mac, or CD-ROM.
 # The default value is: NO.
 
 SHORT_NAMES            = NO
 
-# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen will interpret the
 # first line (until the first dot) of a Javadoc-style comment as the brief
 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
 # style comments (thus requiring an explicit @brief command for a brief
@@ -181,7 +212,17 @@ SHORT_NAMES            = NO
 
 JAVADOC_AUTOBRIEF      = NO
 
-# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
+# If the JAVADOC_BANNER tag is set to YES then Doxygen will interpret a line
+# such as
+# /***************
+# as being the beginning of a Javadoc-style comment "banner". If set to NO, the
+# Javadoc-style will behave just like regular comments and it will not be
+# interpreted by Doxygen.
+# The default value is: NO.
+
+JAVADOC_BANNER         = NO
+
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will interpret the first
 # line (until the first dot) of a Qt-style comment as the brief description. If
 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
 # requiring an explicit \brief command for a brief description.)
@@ -189,7 +230,7 @@ JAVADOC_AUTOBRIEF      = NO
 
 QT_AUTOBRIEF           = NO
 
-# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen treat a
 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
 # a brief description. This used to be the default behavior. The new default is
 # to treat a multi-line C++ comment block as a detailed description. Set this
@@ -201,13 +242,21 @@ QT_AUTOBRIEF           = NO
 
 MULTILINE_CPP_IS_BRIEF = NO
 
+# By default Python docstrings are displayed as preformatted text and Doxygen's
+# special commands cannot be used. By setting PYTHON_DOCSTRING to NO the
+# Doxygen's special commands can be used and the contents of the docstring
+# documentation blocks is shown as Doxygen documentation.
+# The default value is: YES.
+
+PYTHON_DOCSTRING       = YES
+
 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
 # documentation from any documented member that it re-implements.
 # The default value is: YES.
 
 INHERIT_DOCS           = YES
 
-# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
+# If the SEPARATE_MEMBER_PAGES tag is set to YES then Doxygen will produce a new
 # page for each member. If set to NO, the documentation of a member will be part
 # of the file/class/namespace that contains it.
 # The default value is: NO.
@@ -224,20 +273,19 @@ TAB_SIZE               = 8
 # the documentation. An alias has the form:
 # name=value
 # For example adding
-# "sideeffect=@par Side Effects:\n"
+# "sideeffect=@par Side Effects:^^"
 # will allow you to put the command \sideeffect (or @sideeffect) in the
 # documentation, which will result in a user-defined paragraph with heading
-# "Side Effects:". You can put \n's in the value part of an alias to insert
-# newlines.
+# "Side Effects:". Note that you cannot put \n's in the value part of an alias
+# to insert newlines (in the resulting output). You can put ^^ in the value part
+# of an alias to insert a newline as if a physical newline was in the original
+# file. When you need a literal { or } or , in the value part of an alias you
+# have to escape them by means of a backslash (\), this can lead to conflicts
+# with the commands \{ and \} for these it is advised to use the version @{ and
+# @} or use a double escape (\\{ and \\})
 
 ALIASES                =
 
-# This tag can be used to specify a number of word-keyword mappings (TCL only).
-# A mapping has the form "name=value". For example adding "class=itcl::class"
-# will allow you to use the command class in the itcl::class meaning.
-
-# TCL_SUBST              =
-
 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
 # only. Doxygen will then generate output that is more tailored for C. For
 # instance, some of the names that are used will be different. The list of all
@@ -266,36 +314,68 @@ OPTIMIZE_FOR_FORTRAN   = NO
 
 OPTIMIZE_OUTPUT_VHDL   = NO
 
+# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
+# sources only. Doxygen will then generate output that is more tailored for that
+# language. For instance, namespaces will be presented as modules, types will be
+# separated into more groups, etc.
+# The default value is: NO.
+
+OPTIMIZE_OUTPUT_SLICE  = NO
+
 # Doxygen selects the parser to use depending on the extension of the files it
 # parses. With this tag you can assign which parser to use for a given
 # extension. Doxygen has a built-in mapping, but you can override or extend it
 # using this tag. The format is ext=language, where ext is a file extension, and
-# language is one of the parsers supported by doxygen: IDL, Java, Javascript,
-# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
-# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
-# Fortran. In the later case the parser tries to guess whether the code is fixed
-# or free formatted code, this is the default for Fortran type files), VHDL. For
-# instance to make doxygen treat .inc files as Fortran files (default is PHP),
-# and .f files as C (default is Fortran), use: inc=Fortran f=C.
+# language is one of the parsers supported by Doxygen: IDL, Java, JavaScript,
+# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,
+# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
+# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
+# tries to guess whether the code is fixed or free formatted code, this is the
+# default for Fortran type files). For instance to make Doxygen treat .inc files
+# as Fortran files (default is PHP), and .f files as C (default is Fortran),
+# use: inc=Fortran f=C.
 #
 # Note: For files without extension you can use no_extension as a placeholder.
 #
 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
-# the files are not read by doxygen.
+# the files are not read by Doxygen. When specifying no_extension you should add
+# * to the FILE_PATTERNS.
+#
+# Note see also the list of default file extension mappings.
 
 EXTENSION_MAPPING      =
 
-# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
+# If the MARKDOWN_SUPPORT tag is enabled then Doxygen pre-processes all comments
 # according to the Markdown format, which allows for more readable
-# documentation. See http://daringfireball.net/projects/markdown/ for details.
-# The output of markdown processing is further processed by doxygen, so you can
-# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
+# documentation. See https://daringfireball.net/projects/markdown/ for details.
+# The output of markdown processing is further processed by Doxygen, so you can
+# mix Doxygen, HTML, and XML commands with Markdown formatting. Disable only in
 # case of backward compatibilities issues.
 # The default value is: YES.
 
 MARKDOWN_SUPPORT       = YES
 
-# When enabled doxygen tries to link words that correspond to documented
+# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
+# to that level are automatically included in the table of contents, even if
+# they do not have an id attribute.
+# Note: This feature currently applies only to Markdown headings.
+# Minimum value: 0, maximum value: 99, default value: 6.
+# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
+
+TOC_INCLUDE_HEADINGS   = 6
+
+# The MARKDOWN_ID_STYLE tag can be used to specify the algorithm used to
+# generate identifiers for the Markdown headings. Note: Every identifier is
+# unique.
+# Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a
+# sequence number starting at 0 and GITHUB use the lower case version of title
+# with any whitespace replaced by '-' and punctuation characters removed.
+# The default value is: DOXYGEN.
+# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
+
+MARKDOWN_ID_STYLE      = DOXYGEN
+
+# When enabled Doxygen tries to link words that correspond to documented
 # classes, or namespaces to their corresponding documentation. Such a link can
 # be prevented in individual cases by putting a % sign in front of the word or
 # globally by setting AUTOLINK_SUPPORT to NO.
@@ -305,10 +385,10 @@ AUTOLINK_SUPPORT       = YES
 
 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
 # to include (a tag file for) the STL sources as input, then you should set this
-# tag to YES in order to let doxygen match functions declarations and
+# tag to YES in order to let Doxygen match functions declarations and
 # definitions whose arguments contain STL classes (e.g. func(std::string);
-# versus func(std::string) {}). This also make the inheritance and collaboration
-# diagrams that involve STL classes more complete and accurate.
+# versus func(std::string) {}). This also makes the inheritance and
+# collaboration diagrams that involve STL classes more complete and accurate.
 # The default value is: NO.
 
 BUILTIN_STL_SUPPORT    = NO
@@ -320,16 +400,16 @@ BUILTIN_STL_SUPPORT    = NO
 CPP_CLI_SUPPORT        = NO
 
 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
-# http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
-# will parse them like normal C++ but will assume all classes use public instead
-# of private inheritance when no explicit protection keyword is present.
+# https://www.riverbankcomputing.com/software) sources only. Doxygen will parse
+# them like normal C++ but will assume all classes use public instead of private
+# inheritance when no explicit protection keyword is present.
 # The default value is: NO.
 
 SIP_SUPPORT            = NO
 
 # For Microsoft's IDL there are propget and propput attributes to indicate
 # getter and setter methods for a property. Setting this option to YES will make
-# doxygen to replace the get and set methods by a property in the documentation.
+# Doxygen to replace the get and set methods by a property in the documentation.
 # This will only work if the methods are indeed getting or setting a simple
 # type. If this is not the case, or you want to show the methods anyway, you
 # should set this option to NO.
@@ -338,13 +418,20 @@ SIP_SUPPORT            = NO
 IDL_PROPERTY_SUPPORT   = YES
 
 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
-# tag is set to YES then doxygen will reuse the documentation of the first
+# tag is set to YES then Doxygen will reuse the documentation of the first
 # member in the group (if any) for the other members of the group. By default
 # all members of a group must be documented explicitly.
 # The default value is: NO.
 
 DISTRIBUTE_GROUP_DOC   = NO
 
+# If one adds a struct or class to a group and this option is enabled, then also
+# any nested class or struct is added to the same group. By default this option
+# is disabled and one has to add nested compounds explicitly via \ingroup.
+# The default value is: NO.
+
+GROUP_NESTED_COMPOUNDS = NO
+
 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
 # (for instance a group of public functions) to be put as a subgroup of that
 # type (e.g. under the Public Functions section). Set it to NO to prevent
@@ -389,21 +476,42 @@ TYPEDEF_HIDES_STRUCT   = NO
 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
 # cache is used to resolve symbols given their name and scope. Since this can be
 # an expensive process and often the same symbol appears multiple times in the
-# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
-# doxygen will become slower. If the cache is too large, memory is wasted. The
+# code, Doxygen keeps a cache of pre-resolved symbols. If the cache is too small
+# Doxygen will become slower. If the cache is too large, memory is wasted. The
 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
-# symbols. At the end of a run doxygen will report the cache usage and suggest
+# symbols. At the end of a run Doxygen will report the cache usage and suggest
 # the optimal cache size from a speed point of view.
 # Minimum value: 0, maximum value: 9, default value: 0.
 
 LOOKUP_CACHE_SIZE      = 0
 
+# The NUM_PROC_THREADS specifies the number of threads Doxygen is allowed to use
+# during processing. When set to 0 Doxygen will based this on the number of
+# cores available in the system. You can set it explicitly to a value larger
+# than 0 to get more control over the balance between CPU load and processing
+# speed. At this moment only the input processing can be done using multiple
+# threads. Since this is still an experimental feature the default is set to 1,
+# which effectively disables parallel processing. Please report any issues you
+# encounter. Generating dot graphs in parallel is controlled by the
+# DOT_NUM_THREADS setting.
+# Minimum value: 0, maximum value: 32, default value: 1.
+
+NUM_PROC_THREADS       = 1
+
+# If the TIMESTAMP tag is set different from NO then each generated page will
+# contain the date or date and time when the page was generated. Setting this to
+# NO can help when comparing the output of multiple runs.
+# Possible values are: YES, NO, DATETIME and DATE.
+# The default value is: NO.
+
+TIMESTAMP              = NO
+
 #---------------------------------------------------------------------------
 # Build related configuration options
 #---------------------------------------------------------------------------
 
-# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
+# If the EXTRACT_ALL tag is set to YES, Doxygen will assume all entities in
 # documentation are documented, even if no documentation was available. Private
 # class members and static file members will be hidden unless the
 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
@@ -419,6 +527,12 @@ EXTRACT_ALL            = YES
 
 EXTRACT_PRIVATE        = YES
 
+# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual
+# methods of a class will be included in the documentation.
+# The default value is: NO.
+
+EXTRACT_PRIV_VIRTUAL   = NO
+
 # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
 # scope will be included in the documentation.
 # The default value is: NO.
@@ -456,7 +570,14 @@ EXTRACT_LOCAL_METHODS  = YES
 
 EXTRACT_ANON_NSPACES   = NO
 
-# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
+# If this flag is set to YES, the name of an unnamed parameter in a declaration
+# will be determined by the corresponding definition. By default unnamed
+# parameters remain unnamed in the output.
+# The default value is: YES.
+
+RESOLVE_UNNAMED_PARAMS = YES
+
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
 # undocumented members inside documented classes or files. If set to NO these
 # members will be included in the various overviews, but no documentation
 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
@@ -464,22 +585,23 @@ EXTRACT_ANON_NSPACES   = NO
 
 HIDE_UNDOC_MEMBERS     = NO
 
-# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
 # undocumented classes that are normally visible in the class hierarchy. If set
 # to NO, these classes will be included in the various overviews. This option
-# has no effect if EXTRACT_ALL is enabled.
+# will also hide undocumented C++ concepts if enabled. This option has no effect
+# if EXTRACT_ALL is enabled.
 # The default value is: NO.
 
 HIDE_UNDOC_CLASSES     = NO
 
-# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
-# (class|struct|union) declarations. If set to NO, these declarations will be
-# included in the documentation.
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all friend
+# declarations. If set to NO, these declarations will be included in the
+# documentation.
 # The default value is: NO.
 
 HIDE_FRIEND_COMPOUNDS  = NO
 
-# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
 # documentation blocks found inside the body of a function. If set to NO, these
 # blocks will be appended to the function's detailed documentation block.
 # The default value is: NO.
@@ -493,23 +615,44 @@ HIDE_IN_BODY_DOCS      = NO
 
 INTERNAL_DOCS          = NO
 
-# If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
-# names in lower-case letters. If set to YES, upper-case letters are also
-# allowed. This is useful if you have classes or files whose names only differ
-# in case and if your file system supports case sensitive file names. Windows
-# and Mac users are advised to set this option to NO.
-# The default value is: system dependent.
+# With the correct setting of option CASE_SENSE_NAMES Doxygen will better be
+# able to match the capabilities of the underlying filesystem. In case the
+# filesystem is case sensitive (i.e. it supports files in the same directory
+# whose names only differ in casing), the option must be set to YES to properly
+# deal with such files in case they appear in the input. For filesystems that
+# are not case sensitive the option should be set to NO to properly deal with
+# output files written for symbols that only differ in casing, such as for two
+# classes, one named CLASS and the other named Class, and to also support
+# references to files without having to specify the exact matching casing. On
+# Windows (including Cygwin) and macOS, users should typically set this option
+# to NO, whereas on Linux or other Unix flavors it should typically be set to
+# YES.
+# Possible values are: SYSTEM, NO and YES.
+# The default value is: SYSTEM.
 
 CASE_SENSE_NAMES       = YES
 
-# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
+# If the HIDE_SCOPE_NAMES tag is set to NO then Doxygen will show members with
 # their full class and namespace scopes in the documentation. If set to YES, the
 # scope will be hidden.
 # The default value is: NO.
 
 HIDE_SCOPE_NAMES       = NO
 
-# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
+# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then Doxygen will
+# append additional text to a page's title, such as Class Reference. If set to
+# YES the compound reference will be hidden.
+# The default value is: NO.
+
+HIDE_COMPOUND_REFERENCE= NO
+
+# If the SHOW_HEADERFILE tag is set to YES then the documentation for a class
+# will show which file needs to be included to use the class.
+# The default value is: YES.
+
+SHOW_HEADERFILE        = YES
+
+# If the SHOW_INCLUDE_FILES tag is set to YES then Doxygen will put a list of
 # the files that are included by a file in the documentation of that file.
 # The default value is: YES.
 
@@ -522,7 +665,7 @@ SHOW_INCLUDE_FILES     = YES
 
 SHOW_GROUPED_MEMB_INC  = NO
 
-# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen will list include
 # files with double quotes in the documentation rather than with sharp brackets.
 # The default value is: NO.
 
@@ -534,14 +677,14 @@ FORCE_LOCAL_INCLUDES   = NO
 
 INLINE_INFO            = YES
 
-# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
+# If the SORT_MEMBER_DOCS tag is set to YES then Doxygen will sort the
 # (detailed) documentation of file and class members alphabetically by member
 # name. If set to NO, the members will appear in declaration order.
 # The default value is: YES.
 
 SORT_MEMBER_DOCS       = YES
 
-# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
+# If the SORT_BRIEF_DOCS tag is set to YES then Doxygen will sort the brief
 # descriptions of file, namespace and class members alphabetically by member
 # name. If set to NO, the members will appear in declaration order. Note that
 # this will also influence the order of the classes in the class list.
@@ -549,7 +692,7 @@ SORT_MEMBER_DOCS       = YES
 
 SORT_BRIEF_DOCS        = NO
 
-# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then Doxygen will sort the
 # (brief and detailed) documentation of class members so that constructors and
 # destructors are listed first. If set to NO the constructors will appear in the
 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
@@ -561,7 +704,7 @@ SORT_BRIEF_DOCS        = NO
 
 SORT_MEMBERS_CTORS_1ST = NO
 
-# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
+# If the SORT_GROUP_NAMES tag is set to YES then Doxygen will sort the hierarchy
 # of group names into alphabetical order. If set to NO the group names will
 # appear in their defined order.
 # The default value is: NO.
@@ -578,11 +721,11 @@ SORT_GROUP_NAMES       = NO
 
 SORT_BY_SCOPE_NAME     = NO
 
-# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
+# If the STRICT_PROTO_MATCHING option is enabled and Doxygen fails to do proper
 # type resolution of all parameters of a function it will reject a match between
 # the prototype and the implementation of a member function even if there is
 # only one candidate or it is obvious which candidate to choose by doing a
-# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
+# simple string match. By disabling STRICT_PROTO_MATCHING Doxygen will still
 # accept a match between prototype and implementation in such cases.
 # The default value is: NO.
 
@@ -652,24 +795,25 @@ SHOW_FILES             = YES
 SHOW_NAMESPACES        = YES
 
 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
-# doxygen should invoke to get the current version for each file (typically from
+# Doxygen should invoke to get the current version for each file (typically from
 # the version control system). Doxygen will invoke the program by executing (via
 # popen()) the command command input-file, where command is the value of the
 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
-# by doxygen. Whatever the program writes to standard output is used as the file
+# by Doxygen. Whatever the program writes to standard output is used as the file
 # version. For an example see the documentation.
 
 FILE_VERSION_FILTER    =
 
 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
-# by doxygen. The layout file controls the global structure of the generated
+# by Doxygen. The layout file controls the global structure of the generated
 # output files in an output format independent way. To create the layout file
-# that represents doxygen's defaults, run doxygen with the -l option. You can
+# that represents Doxygen's defaults, run Doxygen with the -l option. You can
 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
-# will be used as the name of the layout file.
+# will be used as the name of the layout file. See also section "Changing the
+# layout of pages" for information.
 #
-# Note that if you run doxygen from a directory containing a file called
-# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
+# Note that if you run Doxygen from a directory containing a file called
+# DoxygenLayout.xml, Doxygen will parse it automatically even if the LAYOUT_FILE
 # tag is left empty.
 
 LAYOUT_FILE            =
@@ -677,26 +821,27 @@ LAYOUT_FILE            =
 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
 # the reference definitions. This must be a list of .bib files. The .bib
 # extension is automatically appended if omitted. This requires the bibtex tool
-# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
+# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.
 # For LaTeX the style of the bibliography can be controlled using
 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
 # search path. See also \cite for info how to create references.
 
 CITE_BIB_FILES         =
 
+
 #---------------------------------------------------------------------------
 # Configuration options related to warning and progress messages
 #---------------------------------------------------------------------------
 
 # The QUIET tag can be used to turn on/off the messages that are generated to
-# standard output by doxygen. If QUIET is set to YES this implies that the
+# standard output by Doxygen. If QUIET is set to YES this implies that the
 # messages are off.
 # The default value is: NO.
 
 QUIET                  = NO
 
 # The WARNINGS tag can be used to turn on/off the warning messages that are
-# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
+# generated to standard error (stderr) by Doxygen. If WARNINGS is set to YES
 # this implies that the warnings are on.
 #
 # Tip: Turn warnings on while writing the documentation.
@@ -704,42 +849,89 @@ QUIET                  = NO
 
 WARNINGS               = YES
 
-# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
+# If the WARN_IF_UNDOCUMENTED tag is set to YES then Doxygen will generate
 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
 # will automatically be disabled.
 # The default value is: YES.
 
 WARN_IF_UNDOCUMENTED   = YES
 
-# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
-# potential errors in the documentation, such as not documenting some parameters
-# in a documented function, or documenting parameters that don't exist or using
-# markup commands wrongly.
+# If the WARN_IF_DOC_ERROR tag is set to YES, Doxygen will generate warnings for
+# potential errors in the documentation, such as documenting some parameters in
+# a documented function twice, or documenting parameters that don't exist or
+# using markup commands wrongly.
 # The default value is: YES.
 
 WARN_IF_DOC_ERROR      = YES
 
+# If WARN_IF_INCOMPLETE_DOC is set to YES, Doxygen will warn about incomplete
+# function parameter documentation. If set to NO, Doxygen will accept that some
+# parameters have no documentation without warning.
+# The default value is: YES.
+
+WARN_IF_INCOMPLETE_DOC = YES
+
 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
 # are documented, but have no documentation for their parameters or return
-# value. If set to NO, doxygen will only warn about wrong or incomplete
-# parameter documentation, but not about the absence of documentation.
+# value. If set to NO, Doxygen will only warn about wrong parameter
+# documentation, but not about the absence of documentation. If EXTRACT_ALL is
+# set to YES then this flag will automatically be disabled. See also
+# WARN_IF_INCOMPLETE_DOC
 # The default value is: NO.
 
 WARN_NO_PARAMDOC       = YES
 
-# The WARN_FORMAT tag determines the format of the warning messages that doxygen
+# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, Doxygen will warn about
+# undocumented enumeration values. If set to NO, Doxygen will accept
+# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag
+# will automatically be disabled.
+# The default value is: NO.
+
+WARN_IF_UNDOC_ENUM_VAL = NO
+
+# If the WARN_AS_ERROR tag is set to YES then Doxygen will immediately stop when
+# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS
+# then Doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but
+# at the end of the Doxygen process Doxygen will return with a non-zero status.
+# If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS_PRINT then Doxygen behaves
+# like FAIL_ON_WARNINGS but in case no WARN_LOGFILE is defined Doxygen will not
+# write the warning messages in between other messages but write them at the end
+# of a run, in case a WARN_LOGFILE is defined the warning messages will be
+# besides being in the defined file also be shown at the end of a run, unless
+# the WARN_LOGFILE is defined as - i.e. standard output (stdout) in that case
+# the behavior will remain as with the setting FAIL_ON_WARNINGS.
+# Possible values are: NO, YES, FAIL_ON_WARNINGS and FAIL_ON_WARNINGS_PRINT.
+# The default value is: NO.
+
+WARN_AS_ERROR          = NO
+
+# The WARN_FORMAT tag determines the format of the warning messages that Doxygen
 # can produce. The string should contain the $file, $line, and $text tags, which
 # will be replaced by the file and line number from which the warning originated
 # and the warning text. Optionally the format may contain $version, which will
 # be replaced by the version of the file (if it could be obtained via
 # FILE_VERSION_FILTER)
+# See also: WARN_LINE_FORMAT
 # The default value is: $file:$line: $text.
 
-WARN_FORMAT            = "$file:$line: $text "
+WARN_FORMAT            = "$file:$line: $text"
+
+# In the $text part of the WARN_FORMAT command it is possible that a reference
+# to a more specific place is given. To make it easier to jump to this place
+# (outside of Doxygen) the user can define a custom "cut" / "paste" string.
+# Example:
+# WARN_LINE_FORMAT = "'vi $file +$line'"
+# See also: WARN_FORMAT
+# The default value is: at line $line of file $file.
+
+WARN_LINE_FORMAT       = "at line $line of file $file"
 
 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
 # messages should be written. If left blank the output is written to standard
-# error (stderr).
+# error (stderr). In case the file specified cannot be opened for writing the
+# warning and error messages are written to standard error. When as file - is
+# specified the warning and error messages are written to standard output
+# (stdout).
 
 WARN_LOGFILE           =
 
@@ -750,29 +942,49 @@ WARN_LOGFILE           =
 # The INPUT tag is used to specify the files and/or directories that contain
 # documented source files. You may enter file names like myfile.cpp or
 # directories like /usr/src/myproject. Separate the files or directories with
-# spaces.
+# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
 # Note: If this tag is empty the current directory is searched.
 
 INPUT                  = @abs_top_srcdir@/source/ \
                          @abs_top_srcdir@/include/
 
 # This tag can be used to specify the character encoding of the source files
-# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
+# that Doxygen parses. Internally Doxygen uses the UTF-8 encoding. Doxygen uses
 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
-# documentation (see: http://www.gnu.org/software/libiconv) for the list of
-# possible encodings.
+# documentation (see:
+# https://www.gnu.org/software/libiconv/) for the list of possible encodings.
+# See also: INPUT_FILE_ENCODING
 # The default value is: UTF-8.
 
 INPUT_ENCODING         = UTF-8
 
+# This tag can be used to specify the character encoding of the source files
+# that Doxygen parses The INPUT_FILE_ENCODING tag can be used to specify
+# character encoding on a per file pattern basis. Doxygen will compare the file
+# name with each pattern and apply the encoding instead of the default
+# INPUT_ENCODING) if there is a match. The character encodings are a list of the
+# form: pattern=encoding (like *.php=ISO-8859-1).
+# See also: INPUT_ENCODING for further information on supported encodings.
+
+INPUT_FILE_ENCODING    =
+
 # If the value of the INPUT tag contains directories, you can use the
 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
-# *.h) to filter out the source-files in the directories. If left blank the
-# following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
-# *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
-# *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
-# *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
-# *.qsf, *.as and *.js.
+# *.h) to filter out the source-files in the directories.
+#
+# Note that for custom extensions or not directly supported extensions you also
+# need to set EXTENSION_MAPPING for the extension otherwise the files are not
+# read by Doxygen.
+#
+# Note the list of default checked file patterns might differ from the list of
+# default file extension mappings.
+#
+# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm,
+# *.cpp, *.cppm, *.ccm, *.c++, *.c++m, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl,
+# *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, *.h++, *.ixx, *.l, *.cs, *.d,
+# *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to
+# be provided as Doxygen C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,
+# *.f18, *.f, *.for, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.
 
 FILE_PATTERNS          = *.h \
                          *.c
@@ -787,7 +999,7 @@ RECURSIVE              = YES
 # excluded from the INPUT source files. This way you can easily exclude a
 # subdirectory from a directory tree whose root is specified with the INPUT tag.
 #
-# Note that relative paths are relative to the directory from which doxygen is
+# Note that relative paths are relative to the directory from which Doxygen is
 # run.
 
 EXCLUDE                =
@@ -812,10 +1024,7 @@ EXCLUDE_PATTERNS       =
 # (namespaces, classes, functions, etc.) that should be excluded from the
 # output. The symbol name can be a fully qualified name, a word, or if the
 # wildcard * is used, a substring. Examples: ANamespace, AClass,
-# AClass::ANamespace, ANamespace::*Test
-#
-# Note that the wildcards are matched against the file with absolute path, so to
-# exclude all test directories use the pattern */test/*
+# ANamespace::AClass, ANamespace::*Test
 
 EXCLUDE_SYMBOLS        =
 
@@ -823,7 +1032,7 @@ EXCLUDE_SYMBOLS        =
 # that contain example code fragments that are included (see the \include
 # command).
 
-#EXAMPLE_PATH           = ../example/
+EXAMPLE_PATH           =
 
 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
@@ -845,7 +1054,7 @@ EXAMPLE_RECURSIVE      = YES
 
 IMAGE_PATH             =
 
-# The INPUT_FILTER tag can be used to specify a program that doxygen should
+# The INPUT_FILTER tag can be used to specify a program that Doxygen should
 # invoke to filter for each input file. Doxygen will invoke the filter program
 # by executing (via popen()) the command:
 #
@@ -859,6 +1068,15 @@ IMAGE_PATH             =
 # Note that the filter must not add or remove lines; it is applied before the
 # code is scanned, but not when the output code is generated. If lines are added
 # or removed, the anchors will not be placed correctly.
+#
+# Note that Doxygen will use the data processed and written to standard output
+# for further processing, therefore nothing else, like debug statements or used
+# commands (so in case of a Windows batch file always use @echo OFF), should be
+# written to standard output.
+#
+# Note that for custom extensions or not directly supported extensions you also
+# need to set EXTENSION_MAPPING for the extension otherwise the files are not
+# properly processed by Doxygen.
 
 INPUT_FILTER           =
 
@@ -868,6 +1086,10 @@ INPUT_FILTER           =
 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
 # patterns match the file name, INPUT_FILTER is applied.
+#
+# Note that for custom extensions or not directly supported extensions you also
+# need to set EXTENSION_MAPPING for the extension otherwise the files are not
+# properly processed by Doxygen.
 
 FILTER_PATTERNS        =
 
@@ -889,10 +1111,19 @@ FILTER_SOURCE_PATTERNS =
 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
 # is part of the input, its contents will be placed on the main page
 # (index.html). This can be useful if you have a project on for instance GitHub
-# and want to reuse the introduction page also for the doxygen output.
+# and want to reuse the introduction page also for the Doxygen output.
 
 USE_MDFILE_AS_MAINPAGE =
 
+# The Fortran standard specifies that for fixed formatted Fortran code all
+# characters from position 72 are to be considered as comment. A common
+# extension is to allow longer lines before the automatic comment starts. The
+# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can
+# be processed before the automatic comment starts.
+# Minimum value: 7, maximum value: 10000, default value: 72.
+
+FORTRAN_COMMENT_AFTER  = 72
+
 #---------------------------------------------------------------------------
 # Configuration options related to source browsing
 #---------------------------------------------------------------------------
@@ -907,12 +1138,13 @@ USE_MDFILE_AS_MAINPAGE =
 SOURCE_BROWSER         = YES
 
 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
-# classes and enums directly into the documentation.
+# multi-line macros, enums or list initialized variables directly into the
+# documentation.
 # The default value is: NO.
 
 INLINE_SOURCES         = NO
 
-# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
+# Setting the STRIP_CODE_COMMENTS tag to YES will instruct Doxygen to hide any
 # special comment blocks from generated source code fragments. Normal C, C++ and
 # Fortran comments will always remain visible.
 # The default value is: YES.
@@ -920,7 +1152,7 @@ INLINE_SOURCES         = NO
 STRIP_CODE_COMMENTS    = YES
 
 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
-# function all documented functions referencing it will be listed.
+# entity all documented functions referencing it will be listed.
 # The default value is: NO.
 
 REFERENCED_BY_RELATION = YES
@@ -950,28 +1182,28 @@ REFERENCES_LINK_SOURCE = YES
 SOURCE_TOOLTIPS        = YES
 
 # If the USE_HTAGS tag is set to YES then the references to source code will
-# point to the HTML generated by the htags(1) tool instead of doxygen built-in
+# point to the HTML generated by the htags(1) tool instead of Doxygen built-in
 # source browser. The htags tool is part of GNU's global source tagging system
-# (see http://www.gnu.org/software/global/global.html). You will need version
+# (see https://www.gnu.org/software/global/global.html). You will need version
 # 4.8.6 or higher.
 #
 # To use it do the following:
 # - Install the latest version of global
-# - Enable SOURCE_BROWSER and USE_HTAGS in the config file
+# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
 # - Make sure the INPUT points to the root of the source tree
 # - Run doxygen as normal
 #
 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
 # tools must be available from the command line (i.e. in the search path).
 #
-# The result: instead of the source browser generated by doxygen, the links to
+# The result: instead of the source browser generated by Doxygen, the links to
 # source code will now point to the output of htags.
 # The default value is: NO.
 # This tag requires that the tag SOURCE_BROWSER is set to YES.
 
 USE_HTAGS              = NO
 
-# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
+# If the VERBATIM_HEADERS tag is set the YES then Doxygen will generate a
 # verbatim copy of the header file for each class for which an include is
 # specified. Set to NO to disable this.
 # See also: Section \class.
@@ -979,6 +1211,46 @@ USE_HTAGS              = NO
 
 VERBATIM_HEADERS       = YES
 
+# If the CLANG_ASSISTED_PARSING tag is set to YES then Doxygen will use the
+# clang parser (see:
+# http://clang.llvm.org/) for more accurate parsing at the cost of reduced
+# performance. This can be particularly helpful with template rich C++ code for
+# which Doxygen's built-in parser lacks the necessary type information.
+# Note: The availability of this option depends on whether or not Doxygen was
+# generated with the -Duse_libclang=ON option for CMake.
+# The default value is: NO.
+
+CLANG_ASSISTED_PARSING = NO
+
+# If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS
+# tag is set to YES then Doxygen will add the directory of each input to the
+# include path.
+# The default value is: YES.
+# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
+
+CLANG_ADD_INC_PATHS    = YES
+
+# If clang assisted parsing is enabled you can provide the compiler with command
+# line options that you would normally use when invoking the compiler. Note that
+# the include paths will already be set by Doxygen for the files and directories
+# specified with INPUT and INCLUDE_PATH.
+# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
+
+CLANG_OPTIONS          =
+
+# If clang assisted parsing is enabled you can provide the clang parser with the
+# path to the directory containing a file called compile_commands.json. This
+# file is the compilation database (see:
+# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the
+# options used when the source files were built. This is equivalent to
+# specifying the -p option to a clang tool, such as clang-check. These options
+# will then be passed to the parser. Any options specified with CLANG_OPTIONS
+# will be added as well.
+# Note: The availability of this option depends on whether or not Doxygen was
+# generated with the -Duse_libclang=ON option for CMake.
+
+CLANG_DATABASE_PATH    =
+
 #---------------------------------------------------------------------------
 # Configuration options related to the alphabetical class index
 #---------------------------------------------------------------------------
@@ -990,17 +1262,11 @@ VERBATIM_HEADERS       = YES
 
 ALPHABETICAL_INDEX     = NO
 
-# The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
-# which the alphabetical index list will be split.
-# Minimum value: 1, maximum value: 20, default value: 5.
-# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
-
-#COLS_IN_ALPHA_INDEX    = 5
-
-# In case all classes in a project start with a common prefix, all classes will
-# be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
-# can be used to specify a prefix (or a list of prefixes) that should be ignored
-# while generating the index headers.
+# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes)
+# that should be ignored while generating the index headers. The IGNORE_PREFIX
+# tag works for classes, function and member names. The entity will be placed in
+# the alphabetical list under the first letter of the entity name that remains
+# after removing the prefix.
 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
 
 IGNORE_PREFIX          =
@@ -1009,7 +1275,7 @@ IGNORE_PREFIX          =
 # Configuration options related to the HTML output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
+# If the GENERATE_HTML tag is set to YES, Doxygen will generate HTML output
 # The default value is: YES.
 
 GENERATE_HTML          = YES
@@ -1030,40 +1296,40 @@ HTML_OUTPUT            = html
 HTML_FILE_EXTENSION    = .html
 
 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
-# each generated HTML page. If the tag is left blank doxygen will generate a
+# each generated HTML page. If the tag is left blank Doxygen will generate a
 # standard header.
 #
 # To get valid HTML the header file that includes any scripts and style sheets
-# that doxygen needs, which is dependent on the configuration options used (e.g.
+# that Doxygen needs, which is dependent on the configuration options used (e.g.
 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
 # default header using
 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
 # YourConfigFile
 # and then modify the file new_header.html. See also section "Doxygen usage"
-# for information on how to generate the default header that doxygen normally
+# for information on how to generate the default header that Doxygen normally
 # uses.
 # Note: The header is subject to change so you typically have to regenerate the
-# default header when upgrading to a newer version of doxygen. For a description
+# default header when upgrading to a newer version of Doxygen. For a description
 # of the possible markers and block names see the documentation.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
 HTML_HEADER            =
 
 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
-# generated HTML page. If the tag is left blank doxygen will generate a standard
+# generated HTML page. If the tag is left blank Doxygen will generate a standard
 # footer. See HTML_HEADER for more information on how to generate a default
 # footer and what special commands can be used inside the footer. See also
 # section "Doxygen usage" for information on how to generate the default footer
-# that doxygen normally uses.
+# that Doxygen normally uses.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
 HTML_FOOTER            =
 
 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
 # sheet that is used by each HTML page. It can be used to fine-tune the look of
-# the HTML output. If left blank doxygen will generate a default style sheet.
+# the HTML output. If left blank Doxygen will generate a default style sheet.
 # See also section "Doxygen usage" for information on how to generate the style
-# sheet that doxygen normally uses.
+# sheet that Doxygen normally uses.
 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
 # obsolete.
@@ -1073,13 +1339,18 @@ HTML_STYLESHEET        =
 
 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
 # cascading style sheets that are included after the standard style sheets
-# created by doxygen. Using this option one can overrule certain style aspects.
+# created by Doxygen. Using this option one can overrule certain style aspects.
 # This is preferred over using HTML_STYLESHEET since it does not replace the
 # standard style sheet and is therefore more robust against future updates.
 # Doxygen will copy the style sheet files to the output directory.
 # Note: The order of the extra style sheet files is of importance (e.g. the last
 # style sheet in the list overrules the setting of the previous ones in the
-# list). For an example see the documentation.
+# list).
+# Note: Since the styling of scrollbars can currently not be overruled in
+# Webkit/Chromium, the styling will be left out of the default doxygen.css if
+# one or more extra stylesheets have been specified. So if scrollbar
+# customization is desired it has to be added explicitly. For an example see the
+# documentation.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
 HTML_EXTRA_STYLESHEET  =
@@ -1094,10 +1365,23 @@ HTML_EXTRA_STYLESHEET  =
 
 HTML_EXTRA_FILES       =
 
+# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output
+# should be rendered with a dark or light theme.
+# Possible values are: LIGHT always generates light mode output, DARK always
+# generates dark mode output, AUTO_LIGHT automatically sets the mode according
+# to the user preference, uses light mode if no preference is set (the default),
+# AUTO_DARK automatically sets the mode according to the user preference, uses
+# dark mode if no preference is set and TOGGLE allows a user to switch between
+# light and dark mode via a button.
+# The default value is: AUTO_LIGHT.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_COLORSTYLE        = AUTO_LIGHT
+
 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
 # will adjust the colors in the style sheet and background images according to
-# this color. Hue is specified as an angle on a colorwheel, see
-# http://en.wikipedia.org/wiki/Hue for more information. For instance the value
+# this color. Hue is specified as an angle on a color-wheel, see
+# https://en.wikipedia.org/wiki/Hue for more information. For instance the value
 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
 # purple, and 360 is red again.
 # Minimum value: 0, maximum value: 359, default value: 220.
@@ -1106,7 +1390,7 @@ HTML_EXTRA_FILES       =
 HTML_COLORSTYLE_HUE    = 220
 
 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
-# in the HTML output. For a value of 0 the output will use grayscales only. A
+# in the HTML output. For a value of 0 the output will use gray-scales only. A
 # value of 255 will produce the most vivid colors.
 # Minimum value: 0, maximum value: 255, default value: 100.
 # This tag requires that the tag GENERATE_HTML is set to YES.
@@ -1124,14 +1408,16 @@ HTML_COLORSTYLE_SAT    = 100
 
 HTML_COLORSTYLE_GAMMA  = 80
 
-# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
-# page will contain the date and time when the page was generated. Setting this
-# to YES can help to show when doxygen was last run and thus if the
-# documentation is up to date.
-# The default value is: NO.
+# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML
+# documentation will contain a main index with vertical navigation menus that
+# are dynamically created via JavaScript. If disabled, the navigation index will
+# consists of multiple levels of tabs that are statically embedded in every HTML
+# page. Disable this option to support browsers that do not have JavaScript,
+# like the Qt help browser.
+# The default value is: YES.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
-HTML_TIMESTAMP         = NO
+HTML_DYNAMIC_MENUS     = YES
 
 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
 # documentation will contain sections that can be hidden and shown after the
@@ -1141,6 +1427,14 @@ HTML_TIMESTAMP         = NO
 
 HTML_DYNAMIC_SECTIONS  = NO
 
+# If the HTML_CODE_FOLDING tag is set to YES then classes and functions can be
+# dynamically folded and expanded in the generated HTML source code.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_CODE_FOLDING      = YES
+
+
 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
 # shown in the various tree structured indices initially; the user can expand
 # and collapse entries dynamically later on. Doxygen will expand the tree to
@@ -1156,13 +1450,14 @@ HTML_INDEX_NUM_ENTRIES = 100
 
 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
 # generated that can be used as input for Apple's Xcode 3 integrated development
-# environment (see: http://developer.apple.com/tools/xcode/), introduced with
-# OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
-# Makefile in the HTML output directory. Running make will produce the docset in
-# that directory and running make install will install the docset in
+# environment (see:
+# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To
+# create a documentation set, Doxygen will generate a Makefile in the HTML
+# output directory. Running make will produce the docset in that directory and
+# running make install will install the docset in
 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
-# startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
-# for more information.
+# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
+# genXcode/_index.html for more information.
 # The default value is: NO.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
@@ -1176,6 +1471,13 @@ GENERATE_DOCSET        = NO
 
 DOCSET_FEEDNAME        = "Doxygen generated docs"
 
+# This tag determines the URL of the docset feed. A documentation feed provides
+# an umbrella under which multiple documentation sets from a single provider
+# (such as a company or product suite) can be grouped.
+# This tag requires that the tag GENERATE_DOCSET is set to YES.
+
+DOCSET_FEEDURL         =
+
 # This tag specifies a string that should uniquely identify the documentation
 # set bundle. This should be a reverse domain-name style string, e.g.
 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
@@ -1198,14 +1500,18 @@ DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
 
 DOCSET_PUBLISHER_NAME  = Publisher
 
-# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
+# If the GENERATE_HTMLHELP tag is set to YES then Doxygen generates three
 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
-# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
-# Windows.
+# on Windows. In the beginning of 2021 Microsoft took the original page, with
+# a.o. the download links, offline the HTML help workshop was already many years
+# in maintenance mode). You can download the HTML help workshop from the web
+# archives at Installation executable (see:
+# http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo
+# ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).
 #
 # The HTML Help Workshop contains a compiler that can convert all HTML output
-# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
+# generated by Doxygen into a single compiled HTML file (.chm). Compiled HTML
 # files are now used as the Windows 98 help format, and will replace the old
 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
 # HTML files also contain an index, a table of contents, and you can search for
@@ -1225,14 +1531,14 @@ CHM_FILE               =
 
 # The HHC_LOCATION tag can be used to specify the location (absolute path
 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
-# doxygen will try to run the HTML help compiler on the generated index.hhp.
+# Doxygen will try to run the HTML help compiler on the generated index.hhp.
 # The file has to be specified with full path.
 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 
 HHC_LOCATION           =
 
 # The GENERATE_CHI flag controls if a separate .chi index file is generated
-# (YES) or that it should be included in the master .chm file (NO).
+# (YES) or that it should be included in the main .chm file (NO).
 # The default value is: NO.
 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
 
@@ -1259,6 +1565,16 @@ BINARY_TOC             = NO
 
 TOC_EXPAND             = NO
 
+# The SITEMAP_URL tag is used to specify the full URL of the place where the
+# generated documentation will be placed on the server by the user during the
+# deployment of the documentation. The generated sitemap is called sitemap.xml
+# and placed on the directory specified by HTML_OUTPUT. In case no SITEMAP_URL
+# is specified no sitemap is generated. For information about the sitemap
+# protocol see https://www.sitemaps.org
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+SITEMAP_URL            =
+
 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
@@ -1277,7 +1593,8 @@ QCH_FILE               =
 
 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
 # Project output. For more information please see Qt Help Project / Namespace
-# (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
+# (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
 # The default value is: org.doxygen.Project.
 # This tag requires that the tag GENERATE_QHP is set to YES.
 
@@ -1285,8 +1602,8 @@ QHP_NAMESPACE          = org.doxygen.Project
 
 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
 # Help Project output. For more information please see Qt Help Project / Virtual
-# Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
-# folders).
+# Folders (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).
 # The default value is: doc.
 # This tag requires that the tag GENERATE_QHP is set to YES.
 
@@ -1294,30 +1611,30 @@ QHP_VIRTUAL_FOLDER     = doc
 
 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
 # filter to add. For more information please see Qt Help Project / Custom
-# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
-# filters).
+# Filters (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
 # This tag requires that the tag GENERATE_QHP is set to YES.
 
 QHP_CUST_FILTER_NAME   =
 
 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
 # custom filter to add. For more information please see Qt Help Project / Custom
-# Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
-# filters).
+# Filters (see:
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
 # This tag requires that the tag GENERATE_QHP is set to YES.
 
 QHP_CUST_FILTER_ATTRS  =
 
 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
 # project's filter section matches. Qt Help Project / Filter Attributes (see:
-# http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
+# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
 # This tag requires that the tag GENERATE_QHP is set to YES.
 
 QHP_SECT_FILTER_ATTRS  =
 
-# The QHG_LOCATION tag can be used to specify the location of Qt's
-# qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
-# generated .qhp file.
+# The QHG_LOCATION tag can be used to specify the location (absolute path
+# including file name) of Qt's qhelpgenerator. If non-empty Doxygen will try to
+# run qhelpgenerator on the generated .qhp file.
 # This tag requires that the tag GENERATE_QHP is set to YES.
 
 QHG_LOCATION           =
@@ -1360,18 +1677,30 @@ DISABLE_INDEX          = NO
 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
 # (i.e. any modern browser). Windows users are probably better off using the
 # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
-# further fine-tune the look of the index. As an example, the default style
-# sheet generated by doxygen has an example that shows how to put an image at
-# the root of the tree instead of the PROJECT_NAME. Since the tree basically has
-# the same information as the tab index, you could consider setting
-# DISABLE_INDEX to YES when enabling this option.
+# further fine tune the look of the index (see "Fine-tuning the output"). As an
+# example, the default style sheet generated by Doxygen has an example that
+# shows how to put an image at the root of the tree instead of the PROJECT_NAME.
+# Since the tree basically has the same information as the tab index, you could
+# consider setting DISABLE_INDEX to YES when enabling this option.
 # The default value is: NO.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
 GENERATE_TREEVIEW      = YES
 
+# When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the
+# FULL_SIDEBAR option determines if the side bar is limited to only the treeview
+# area (value NO) or if it should extend to the full height of the window (value
+# YES). Setting this to YES gives a layout similar to
+# https://docs.readthedocs.io with more room for contents, but less room for the
+# project logo, title, and description. If either GENERATE_TREEVIEW or
+# DISABLE_INDEX is set to NO, this option has no effect.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+FULL_SIDEBAR           = NO
+
 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
-# doxygen will group on one line in the generated HTML documentation.
+# Doxygen will group on one line in the generated HTML documentation.
 #
 # Note that a value of 0 will completely suppress the enum values from appearing
 # in the overview section.
@@ -1380,6 +1709,7 @@ GENERATE_TREEVIEW      = YES
 
 ENUM_VALUES_PER_LINE   = 4
 
+
 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
 # to set the initial width (in pixels) of the frame in which the tree is shown.
 # Minimum value: 0, maximum value: 1500, default value: 250.
@@ -1387,35 +1717,48 @@ ENUM_VALUES_PER_LINE   = 4
 
 TREEVIEW_WIDTH         = 250
 
-# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to
+# If the EXT_LINKS_IN_WINDOW option is set to YES, Doxygen will open links to
 # external symbols imported via tag files in a separate window.
 # The default value is: NO.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
 EXT_LINKS_IN_WINDOW    = NO
 
+# If the OBFUSCATE_EMAILS tag is set to YES, Doxygen will obfuscate email
+# addresses.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+OBFUSCATE_EMAILS       = YES
+
+# If the HTML_FORMULA_FORMAT option is set to svg, Doxygen will use the pdf2svg
+# tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see
+# https://inkscape.org) to generate formulas as SVG images instead of PNGs for
+# the HTML output. These images will generally look nicer at scaled resolutions.
+# Possible values are: png (the default) and svg (looks nicer but requires the
+# pdf2svg or inkscape tool).
+# The default value is: png.
+# This tag requires that the tag GENERATE_HTML is set to YES.
+
+HTML_FORMULA_FORMAT    = png
+
 # Use this tag to change the font size of LaTeX formulas included as images in
 # the HTML documentation. When you change the font size after a successful
-# doxygen run you need to manually remove any form_*.png images from the HTML
+# Doxygen run you need to manually remove any form_*.png images from the HTML
 # output directory to force them to be regenerated.
 # Minimum value: 8, maximum value: 50, default value: 10.
 # This tag requires that the tag GENERATE_HTML is set to YES.
 
 FORMULA_FONTSIZE       = 10
 
-# Use the FORMULA_TRANPARENT tag to determine whether or not the images
-# generated for formulas are transparent PNGs. Transparent PNGs are not
-# supported properly for IE 6.0, but are supported on all modern browsers.
-#
-# Note that when changing this option you need to delete any form_*.png files in
-# the HTML output directory before the changes have effect.
-# The default value is: YES.
-# This tag requires that the tag GENERATE_HTML is set to YES.
+# The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands
+# to create new LaTeX commands to be used in formulas as building blocks. See
+# the section "Including formulas" for details.
 
-FORMULA_TRANSPARENT    = YES
+FORMULA_MACROFILE      =
 
 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
-# http://www.mathjax.org) which uses client side Javascript for the rendering
+# https://www.mathjax.org) which uses client side JavaScript for the rendering
 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
 # installed or if you want to formulas look prettier in the HTML output. When
 # enabled you may also need to install MathJax separately and configure the path
@@ -1425,11 +1768,29 @@ FORMULA_TRANSPARENT    = YES
 
 USE_MATHJAX            = NO
 
+# With MATHJAX_VERSION it is possible to specify the MathJax version to be used.
+# Note that the different versions of MathJax have different requirements with
+# regards to the different settings, so it is possible that also other MathJax
+# settings have to be changed when switching between the different MathJax
+# versions.
+# Possible values are: MathJax_2 and MathJax_3.
+# The default value is: MathJax_2.
+# This tag requires that the tag USE_MATHJAX is set to YES.
+
+MATHJAX_VERSION        = MathJax_2
+
 # When MathJax is enabled you can set the default output format to be used for
-# the MathJax output. See the MathJax site (see:
-# http://docs.mathjax.org/en/latest/output.html) for more details.
+# the MathJax output. For more details about the output format see MathJax
+# version 2 (see:
+# http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3
+# (see:
+# http://docs.mathjax.org/en/latest/web/components/output.html).
 # Possible values are: HTML-CSS (which is slower, but has the best
-# compatibility), NativeMML (i.e. MathML) and SVG.
+# compatibility. This is the name for Mathjax version 2, for MathJax version 3
+# this will be translated into chtml), NativeMML (i.e. MathML. Only supported
+# for MathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This
+# is the name for Mathjax version 3, for MathJax version 2 this will be
+# translated into HTML-CSS) and SVG.
 # The default value is: HTML-CSS.
 # This tag requires that the tag USE_MATHJAX is set to YES.
 
@@ -1442,33 +1803,40 @@ MATHJAX_FORMAT         = HTML-CSS
 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
 # Content Delivery Network so you can quickly see the result without installing
 # MathJax. However, it is strongly recommended to install a local copy of
-# MathJax from http://www.mathjax.org before deployment.
-# The default value is: http://cdn.mathjax.org/mathjax/latest.
+# MathJax from https://www.mathjax.org before deployment. The default value is:
+# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2
+# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3
 # This tag requires that the tag USE_MATHJAX is set to YES.
 
 MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest
 
 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
 # extension names that should be enabled during MathJax rendering. For example
+# for MathJax version 2 (see
+# https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions):
 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
+# For example for MathJax version 3 (see
+# http://docs.mathjax.org/en/latest/input/tex/extensions/index.html):
+# MATHJAX_EXTENSIONS = ams
 # This tag requires that the tag USE_MATHJAX is set to YES.
 
 MATHJAX_EXTENSIONS     =
 
-# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
+# The MATHJAX_CODEFILE tag can be used to specify a file with JavaScript pieces
 # of code that will be used on startup of the MathJax code. See the MathJax site
-# (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
+# (see:
+# http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an
 # example see the documentation.
 # This tag requires that the tag USE_MATHJAX is set to YES.
 
 MATHJAX_CODEFILE       =
 
-# When the SEARCHENGINE tag is enabled doxygen will generate a search box for
-# the HTML output. The underlying search engine uses javascript and DHTML and
+# When the SEARCHENGINE tag is enabled Doxygen will generate a search box for
+# the HTML output. The underlying search engine uses JavaScript and DHTML and
 # should work on any modern browser. Note that when using HTML help
 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
 # there is already a search function so this one should typically be disabled.
-# For large projects the javascript based search engine can be slow, then
+# For large projects the JavaScript based search engine can be slow, then
 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
 # search using the keyboard; to jump to the search box use <access key> + S
 # (what the <access key> is depends on the OS and browser, but it is typically
@@ -1485,9 +1853,9 @@ MATHJAX_CODEFILE       =
 SEARCHENGINE           = NO
 
 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
-# implemented using a web server instead of a web client using Javascript. There
+# implemented using a web server instead of a web client using JavaScript. There
 # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
-# setting. When disabled, doxygen will generate a PHP script for searching and
+# setting. When disabled, Doxygen will generate a PHP script for searching and
 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
 # and searching needs to be provided by external tools. See the section
 # "External Indexing and Searching" for details.
@@ -1496,7 +1864,7 @@ SEARCHENGINE           = NO
 
 SERVER_BASED_SEARCH    = NO
 
-# When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
+# When EXTERNAL_SEARCH tag is enabled Doxygen will no longer generate the PHP
 # script for searching. Instead the search results are written to an XML file
 # which needs to be processed by an external indexer. Doxygen will invoke an
 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
@@ -1504,7 +1872,8 @@ SERVER_BASED_SEARCH    = NO
 #
 # Doxygen ships with an example indexer (doxyindexer) and search engine
 # (doxysearch.cgi) which are based on the open source search engine library
-# Xapian (see: http://xapian.org/).
+# Xapian (see:
+# https://xapian.org/).
 #
 # See the section "External Indexing and Searching" for details.
 # The default value is: NO.
@@ -1517,8 +1886,9 @@ EXTERNAL_SEARCH        = NO
 #
 # Doxygen ships with an example indexer (doxyindexer) and search engine
 # (doxysearch.cgi) which are based on the open source search engine library
-# Xapian (see: http://xapian.org/). See the section "External Indexing and
-# Searching" for details.
+# Xapian (see:
+# https://xapian.org/). See the section "External Indexing and Searching" for
+# details.
 # This tag requires that the tag SEARCHENGINE is set to YES.
 
 SEARCHENGINE_URL       =
@@ -1539,7 +1909,7 @@ SEARCHDATA_FILE        = searchdata.xml
 
 EXTERNAL_SEARCH_ID     =
 
-# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
+# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through Doxygen
 # projects other than the one defined by this configuration file, but that are
 # all added to the same external search index. Each project needs to have a
 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
@@ -1553,7 +1923,7 @@ EXTRA_SEARCH_MAPPINGS  =
 # Configuration options related to the LaTeX output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
+# If the GENERATE_LATEX tag is set to YES, Doxygen will generate LaTeX output.
 # The default value is: YES.
 
 GENERATE_LATEX         = NO
@@ -1569,22 +1939,36 @@ LATEX_OUTPUT           = latex
 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
 # invoked.
 #
-# Note that when enabling USE_PDFLATEX this option is only used for generating
-# bitmaps for formulas in the HTML output, but not in the Makefile that is
-# written to the output directory.
-# The default file is: latex.
+# Note that when not enabling USE_PDFLATEX the default is latex when enabling
+# USE_PDFLATEX the default is pdflatex and when in the later case latex is
+# chosen this is overwritten by pdflatex. For specific output languages the
+# default can have been set differently, this depends on the implementation of
+# the output language.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 LATEX_CMD_NAME         = latex
 
 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
 # index for LaTeX.
+# Note: This tag is used in the Makefile / make.bat.
+# See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
+# (.tex).
 # The default file is: makeindex.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 MAKEINDEX_CMD_NAME     = makeindex
 
-# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
+# The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
+# generate index for LaTeX. In case there is no backslash (\) as first character
+# it will be automatically added in the LaTeX code.
+# Note: This tag is used in the generated output file (.tex).
+# See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
+# The default value is: makeindex.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_MAKEINDEX_CMD    = makeindex
+
+# If the COMPACT_LATEX tag is set to YES, Doxygen generates more compact LaTeX
 # documents. This may be useful for small projects and may help to save some
 # trees in general.
 # The default value is: NO.
@@ -1599,44 +1983,60 @@ COMPACT_LATEX          = NO
 # The default value is: a4.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
-#PAPER_TYPE             = a4wide
+PAPER_TYPE             = a4
 
 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
-# that should be included in the LaTeX output. To get the times font for
-# instance you can specify
-# EXTRA_PACKAGES=times
+# that should be included in the LaTeX output. The package can be specified just
+# by its name or with the correct syntax as to be used with the LaTeX
+# \usepackage command. To get the times font for instance you can specify :
+# EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
+# To use the option intlimits with the amsmath package you can specify:
+# EXTRA_PACKAGES=[intlimits]{amsmath}
 # If left blank no extra packages will be included.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 EXTRA_PACKAGES         =
 
-# The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
-# generated LaTeX document. The header should contain everything until the first
-# chapter. If it is left blank doxygen will generate a standard header. See
-# section "Doxygen usage" for information on how to let doxygen write the
-# default header to a separate file.
+# The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for
+# the generated LaTeX document. The header should contain everything until the
+# first chapter. If it is left blank Doxygen will generate a standard header. It
+# is highly recommended to start with a default header using
+# doxygen -w latex new_header.tex new_footer.tex new_stylesheet.sty
+# and then modify the file new_header.tex. See also section "Doxygen usage" for
+# information on how to generate the default header that Doxygen normally uses.
 #
-# Note: Only use a user-defined header if you know what you are doing! The
-# following commands have a special meaning inside the header: $title,
-# $datetime, $date, $doxygenversion, $projectname, $projectnumber,
-# $projectbrief, $projectlogo. Doxygen will replace $title with the empty
-# string, for the replacement values of the other commands the user is referred
-# to HTML_HEADER.
+# Note: Only use a user-defined header if you know what you are doing!
+# Note: The header is subject to change so you typically have to regenerate the
+# default header when upgrading to a newer version of Doxygen. The following
+# commands have a special meaning inside the header (and footer): For a
+# description of the possible markers and block names see the documentation.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 LATEX_HEADER           =
 
-# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
-# generated LaTeX document. The footer should contain everything after the last
-# chapter. If it is left blank doxygen will generate a standard footer. See
+# The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for
+# the generated LaTeX document. The footer should contain everything after the
+# last chapter. If it is left blank Doxygen will generate a standard footer. See
 # LATEX_HEADER for more information on how to generate a default footer and what
-# special commands can be used inside the footer.
-#
-# Note: Only use a user-defined footer if you know what you are doing!
+# special commands can be used inside the footer. See also section "Doxygen
+# usage" for information on how to generate the default footer that Doxygen
+# normally uses. Note: Only use a user-defined footer if you know what you are
+# doing!
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 LATEX_FOOTER           =
 
+# The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
+# LaTeX style sheets that are included after the standard style sheets created
+# by Doxygen. Using this option one can overrule certain style aspects. Doxygen
+# will copy the style sheet files to the output directory.
+# Note: The order of the extra style sheet files is of importance (e.g. the last
+# style sheet in the list overrules the setting of the previous ones in the
+# list).
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_EXTRA_STYLESHEET =
+
 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
 # other source files which should be copied to the LATEX_OUTPUT output
 # directory. Note that the files will be copied as-is; there are no commands or
@@ -1654,53 +2054,59 @@ LATEX_EXTRA_FILES      =
 
 PDF_HYPERLINKS         = YES
 
-# If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
-# the PDF file directly from the LaTeX files. Set this option to YES, to get a
-# higher quality PDF documentation.
+# If the USE_PDFLATEX tag is set to YES, Doxygen will use the engine as
+# specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX
+# files. Set this option to YES, to get a higher quality PDF documentation.
+#
+# See also section LATEX_CMD_NAME for selecting the engine.
 # The default value is: YES.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 USE_PDFLATEX           = YES
 
-# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
-# command to the generated LaTeX files. This will instruct LaTeX to keep running
-# if errors occur, instead of asking the user for help. This option is also used
-# when generating formulas in HTML.
+# The LATEX_BATCHMODE tag signals the behavior of LaTeX in case of an error.
+# Possible values are: NO same as ERROR_STOP, YES same as BATCH, BATCH In batch
+# mode nothing is printed on the terminal, errors are scrolled as if <return> is
+# hit at every error; missing files that TeX tries to input or request from
+# keyboard input (\read on a not open input stream) cause the job to abort,
+# NON_STOP In nonstop mode the diagnostic message will appear on the terminal,
+# but there is no possibility of user interaction just like in batch mode,
+# SCROLL In scroll mode, TeX will stop only for missing files to input or if
+# keyboard input is necessary and ERROR_STOP In errorstop mode, TeX will stop at
+# each error, asking for user intervention.
 # The default value is: NO.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 LATEX_BATCHMODE        = NO
 
-# If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
+# If the LATEX_HIDE_INDICES tag is set to YES then Doxygen will not include the
 # index chapters (such as File Index, Compound Index, etc.) in the output.
 # The default value is: NO.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 LATEX_HIDE_INDICES     = NO
 
-# If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
-# code with syntax highlighting in the LaTeX output.
-#
-# Note that which sources are shown also depends on other settings such as
-# SOURCE_BROWSER.
-# The default value is: NO.
-# This tag requires that the tag GENERATE_LATEX is set to YES.
-
-LATEX_SOURCE_CODE      = NO
-
 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
 # bibliography, e.g. plainnat, or ieeetr. See
-# http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
+# https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
 # The default value is: plain.
 # This tag requires that the tag GENERATE_LATEX is set to YES.
 
 LATEX_BIB_STYLE        = plain
 
+# The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
+# path from which the emoji images will be read. If a relative path is entered,
+# it will be relative to the LATEX_OUTPUT directory. If left blank the
+# LATEX_OUTPUT directory will be used.
+# This tag requires that the tag GENERATE_LATEX is set to YES.
+
+LATEX_EMOJI_DIRECTORY  =
+
 #---------------------------------------------------------------------------
 # Configuration options related to the RTF output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
+# If the GENERATE_RTF tag is set to YES, Doxygen will generate RTF output. The
 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
 # readers/editors.
 # The default value is: NO.
@@ -1715,7 +2121,7 @@ GENERATE_RTF           = NO
 
 RTF_OUTPUT             = rtf
 
-# If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
+# If the COMPACT_RTF tag is set to YES, Doxygen generates more compact RTF
 # documents. This may be useful for small projects and may help to save some
 # trees in general.
 # The default value is: NO.
@@ -1735,29 +2141,28 @@ COMPACT_RTF            = NO
 
 RTF_HYPERLINKS         = NO
 
-# Load stylesheet definitions from file. Syntax is similar to doxygen's config
-# file, i.e. a series of assignments. You only have to provide replacements,
-# missing definitions are set to their default value.
+# Load stylesheet definitions from file. Syntax is similar to Doxygen's
+# configuration file, i.e. a series of assignments. You only have to provide
+# replacements, missing definitions are set to their default value.
 #
 # See also section "Doxygen usage" for information on how to generate the
-# default style sheet that doxygen normally uses.
+# default style sheet that Doxygen normally uses.
 # This tag requires that the tag GENERATE_RTF is set to YES.
 
 RTF_STYLESHEET_FILE    =
 
 # Set optional variables used in the generation of an RTF document. Syntax is
-# similar to doxygen's config file. A template extensions file can be generated
-# using doxygen -e rtf extensionFile.
+# similar to Doxygen's configuration file. A template extensions file can be
+# generated using doxygen -e rtf extensionFile.
 # This tag requires that the tag GENERATE_RTF is set to YES.
 
 RTF_EXTENSIONS_FILE    =
 
-
 #---------------------------------------------------------------------------
 # Configuration options related to the man page output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
+# If the GENERATE_MAN tag is set to YES, Doxygen will generate man pages for
 # classes and files.
 # The default value is: NO.
 
@@ -1781,7 +2186,14 @@ MAN_OUTPUT             = man
 
 MAN_EXTENSION          = .3
 
-# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
+# The MAN_SUBDIR tag determines the name of the directory created within
+# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
+# MAN_EXTENSION with the initial . removed.
+# This tag requires that the tag GENERATE_MAN is set to YES.
+
+MAN_SUBDIR             =
+
+# If the MAN_LINKS tag is set to YES and Doxygen generates man output, then it
 # will generate one additional man file for each entity documented in the real
 # man page(s). These additional files only source the real man page, but without
 # them the man command would be unable to find the correct page.
@@ -1794,7 +2206,7 @@ MAN_LINKS              = NO
 # Configuration options related to the XML output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
+# If the GENERATE_XML tag is set to YES, Doxygen will generate an XML file that
 # captures the structure of the code including all documentation.
 # The default value is: NO.
 
@@ -1808,7 +2220,7 @@ GENERATE_XML           = YES
 
 XML_OUTPUT             = xml
 
-# If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
+# If the XML_PROGRAMLISTING tag is set to YES, Doxygen will dump the program
 # listings (including syntax highlighting and cross-referencing information) to
 # the XML output. Note that enabling this will significantly increase the size
 # of the XML output.
@@ -1817,11 +2229,18 @@ XML_OUTPUT             = xml
 
 XML_PROGRAMLISTING     = YES
 
+# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, Doxygen will include
+# namespace members in file scope as well, matching the HTML output.
+# The default value is: NO.
+# This tag requires that the tag GENERATE_XML is set to YES.
+
+XML_NS_MEMB_FILE_SCOPE = NO
+
 #---------------------------------------------------------------------------
 # Configuration options related to the DOCBOOK output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
+# If the GENERATE_DOCBOOK tag is set to YES, Doxygen will generate Docbook files
 # that can be used to generate PDF.
 # The default value is: NO.
 
@@ -1835,24 +2254,49 @@ GENERATE_DOCBOOK       = NO
 
 DOCBOOK_OUTPUT         = docbook
 
-
 #---------------------------------------------------------------------------
 # Configuration options for the AutoGen Definitions output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
-# AutoGen Definitions (see http://autogen.sf.net) file that captures the
-# structure of the code including all documentation. Note that this feature is
-# still experimental and incomplete at the moment.
+# If the GENERATE_AUTOGEN_DEF tag is set to YES, Doxygen will generate an
+# AutoGen Definitions (see https://autogen.sourceforge.net/) file that captures
+# the structure of the code including all documentation. Note that this feature
+# is still experimental and incomplete at the moment.
 # The default value is: NO.
 
 GENERATE_AUTOGEN_DEF   = NO
 
+#---------------------------------------------------------------------------
+# Configuration options related to Sqlite3 output
+#---------------------------------------------------------------------------
+
+# If the GENERATE_SQLITE3 tag is set to YES Doxygen will generate a Sqlite3
+# database with symbols found by Doxygen stored in tables.
+# The default value is: NO.
+
+GENERATE_SQLITE3       = NO
+
+# The SQLITE3_OUTPUT tag is used to specify where the Sqlite3 database will be
+# put. If a relative path is entered the value of OUTPUT_DIRECTORY will be put
+# in front of it.
+# The default directory is: sqlite3.
+# This tag requires that the tag GENERATE_SQLITE3 is set to YES.
+
+SQLITE3_OUTPUT         = sqlite3
+
+# The SQLITE3_RECREATE_DB tag is set to YES, the existing doxygen_sqlite3.db
+# database file will be recreated with each Doxygen run. If set to NO, Doxygen
+# will warn if a database file is already found and not modify it.
+# The default value is: YES.
+# This tag requires that the tag GENERATE_SQLITE3 is set to YES.
+
+SQLITE3_RECREATE_DB    = YES
+
 #---------------------------------------------------------------------------
 # Configuration options related to the Perl module output
 #---------------------------------------------------------------------------
 
-# If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
+# If the GENERATE_PERLMOD tag is set to YES, Doxygen will generate a Perl module
 # file that captures the structure of the code including all documentation.
 #
 # Note that this feature is still experimental and incomplete at the moment.
@@ -1860,7 +2304,7 @@ GENERATE_AUTOGEN_DEF   = NO
 
 GENERATE_PERLMOD       = NO
 
-# If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
+# If the PERLMOD_LATEX tag is set to YES, Doxygen will generate the necessary
 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
 # output from the Perl module output.
 # The default value is: NO.
@@ -1890,13 +2334,13 @@ PERLMOD_MAKEVAR_PREFIX =
 # Configuration options related to the preprocessor
 #---------------------------------------------------------------------------
 
-# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
+# If the ENABLE_PREPROCESSING tag is set to YES, Doxygen will evaluate all
 # C-preprocessor directives found in the sources and include files.
 # The default value is: YES.
 
 ENABLE_PREPROCESSING   = YES
 
-# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
+# If the MACRO_EXPANSION tag is set to YES, Doxygen will expand all macro names
 # in the source code. If set to NO, only conditional compilation will be
 # performed. Macro expansion can be done in a controlled way by setting
 # EXPAND_ONLY_PREDEF to YES.
@@ -1922,7 +2366,8 @@ SEARCH_INCLUDES        = YES
 
 # The INCLUDE_PATH tag can be used to specify one or more directories that
 # contain include files that are not input files but should be processed by the
-# preprocessor.
+# preprocessor. Note that the INCLUDE_PATH is not recursive, so the setting of
+# RECURSIVE has no effect here.
 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
 
 INCLUDE_PATH           =
@@ -1954,7 +2399,7 @@ PREDEFINED             =
 
 EXPAND_AS_DEFINED      =
 
-# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
+# If the SKIP_FUNCTION_MACROS tag is set to YES then Doxygen's preprocessor will
 # remove all references to function-like macros that are alone on a line, have
 # an all uppercase name, and do not end with a semicolon. Such function macros
 # are typically used for boiler-plate code, and will confuse the parser if not
@@ -1978,26 +2423,26 @@ SKIP_FUNCTION_MACROS   = YES
 # section "Linking to external documentation" for more information about the use
 # of tag files.
 # Note: Each tag file must have a unique name (where the name does NOT include
-# the path). If a tag file is not located in the directory in which doxygen is
+# the path). If a tag file is not located in the directory in which Doxygen is
 # run, you must also specify the path to the tagfile here.
 
 TAGFILES               =
 
-# When a file name is specified after GENERATE_TAGFILE, doxygen will create a
+# When a file name is specified after GENERATE_TAGFILE, Doxygen will create a
 # tag file that is based on the input files it reads. See section "Linking to
 # external documentation" for more information about the usage of tag files.
 
 GENERATE_TAGFILE       =
 
-# If the ALLEXTERNALS tag is set to YES, all external class will be listed in
-# the class index. If set to NO, only the inherited external classes will be
-# listed.
+# If the ALLEXTERNALS tag is set to YES, all external classes and namespaces
+# will be listed in the class and namespace index. If set to NO, only the
+# inherited external classes will be listed.
 # The default value is: NO.
 
 ALLEXTERNALS           = NO
 
 # If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
-# in the modules index. If set to NO, only the current project's groups will be
+# in the topic index. If set to NO, only the current project's groups will be
 # listed.
 # The default value is: YES.
 
@@ -2011,42 +2456,26 @@ EXTERNAL_GROUPS        = YES
 EXTERNAL_PAGES         = YES
 
 #---------------------------------------------------------------------------
-# Configuration options related to the dot tool
+# Configuration options related to diagram generator tools
 #---------------------------------------------------------------------------
 
-# If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
-# (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
-# NO turns the diagrams off. Note that this option also works with HAVE_DOT
-# disabled, but it is recommended to install and use dot, since it yields more
-# powerful graphs.
-# The default value is: YES.
-
-CLASS_DIAGRAMS         = YES
-
-# You can include diagrams made with dia in doxygen documentation. Doxygen will
-# then run dia to produce the diagram and insert it in the documentation. The
-# DIA_PATH tag allows you to specify the directory where the dia binary resides.
-# If left empty dia is assumed to be found in the default search path.
-
-DIA_PATH               =
-
 # If set to YES the inheritance and collaboration graphs will hide inheritance
 # and usage relations if the target is undocumented or is not a class.
 # The default value is: YES.
 
 HIDE_UNDOC_RELATIONS   = YES
 
-# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
+# If you set the HAVE_DOT tag to YES then Doxygen will assume the dot tool is
 # available from the path. This tool is part of Graphviz (see:
-# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
+# https://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
 # Bell Labs. The other options in this section have no effect if this option is
 # set to NO
-# The default value is: YES.
+# The default value is: NO.
 
 HAVE_DOT               = YES
 
-# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
-# to run in parallel. When set to 0 doxygen will base this on the number of
+# The DOT_NUM_THREADS specifies the number of dot invocations Doxygen is allowed
+# to run in parallel. When set to 0 Doxygen will base this on the number of
 # processors available in the system. You can set it explicitly to a value
 # larger than 0 to get control over the balance between CPU load and processing
 # speed.
@@ -2055,55 +2484,83 @@ HAVE_DOT               = YES
 
 DOT_NUM_THREADS        = 0
 
-# When you want a differently looking font in the dot files that doxygen
-# generates you can specify the font name using DOT_FONTNAME. You need to make
-# sure dot is able to find the font, which can be done by putting it in a
-# standard location or by setting the DOTFONTPATH environment variable or by
-# setting DOT_FONTPATH to the directory containing the font.
-# The default value is: Helvetica.
+# DOT_COMMON_ATTR is common attributes for nodes, edges and labels of
+# subgraphs. When you want a differently looking font in the dot files that
+# Doxygen generates you can specify fontname, fontcolor and fontsize attributes.
+# For details please see <a href=https://graphviz.org/doc/info/attrs.html>Node,
+# Edge and Graph Attributes specification</a> You need to make sure dot is able
+# to find the font, which can be done by putting it in a standard location or by
+# setting the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the
+# directory containing the font. Default graphviz fontsize is 14.
+# The default value is: fontname=Helvetica,fontsize=10.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
-DOT_FONTNAME           = Helvetica
+DOT_COMMON_ATTR        = "fontname=Helvetica,fontsize=10"
 
-# The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
-# dot graphs.
-# Minimum value: 4, maximum value: 24, default value: 10.
+# DOT_EDGE_ATTR is concatenated with DOT_COMMON_ATTR. For elegant style you can
+# add 'arrowhead=open, arrowtail=open, arrowsize=0.5'. <a
+# href=https://graphviz.org/doc/info/arrows.html>Complete documentation about
+# arrows shapes.</a>
+# The default value is: labelfontname=Helvetica,labelfontsize=10.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
-DOT_FONTSIZE           = 10
+DOT_EDGE_ATTR          = "labelfontname=Helvetica,labelfontsize=10"
 
-# By default doxygen will tell dot to use the default font as specified with
-# DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
-# the path where dot can find it using this tag.
+# DOT_NODE_ATTR is concatenated with DOT_COMMON_ATTR. For view without boxes
+# around nodes set 'shape=plain' or 'shape=plaintext' <a
+# href=https://www.graphviz.org/doc/info/shapes.html>Shapes specification</a>
+# The default value is: shape=box,height=0.2,width=0.4.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_NODE_ATTR          = "shape=box,height=0.2,width=0.4"
+
+# You can set the path where dot can find font specified with fontname in
+# DOT_COMMON_ATTR and others dot attributes.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 DOT_FONTPATH           =
 
-# If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
-# each documented class showing the direct and indirect inheritance relations.
-# Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
+# If the CLASS_GRAPH tag is set to YES or GRAPH or BUILTIN then Doxygen will
+# generate a graph for each documented class showing the direct and indirect
+# inheritance relations. In case the CLASS_GRAPH tag is set to YES or GRAPH and
+# HAVE_DOT is enabled as well, then dot will be used to draw the graph. In case
+# the CLASS_GRAPH tag is set to YES and HAVE_DOT is disabled or if the
+# CLASS_GRAPH tag is set to BUILTIN, then the built-in generator will be used.
+# If the CLASS_GRAPH tag is set to TEXT the direct and indirect inheritance
+# relations will be shown as texts / links. Explicit enabling an inheritance
+# graph or choosing a different representation for an inheritance graph of a
+# specific class, can be accomplished by means of the command \inheritancegraph.
+# Disabling an inheritance graph can be accomplished by means of the command
+# \hideinheritancegraph.
+# Possible values are: NO, YES, TEXT, GRAPH and BUILTIN.
 # The default value is: YES.
-# This tag requires that the tag HAVE_DOT is set to YES.
 
 CLASS_GRAPH            = YES
 
-# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
+# If the COLLABORATION_GRAPH tag is set to YES then Doxygen will generate a
 # graph for each documented class showing the direct and indirect implementation
 # dependencies (inheritance, containment, and class references variables) of the
-# class with other documented classes.
+# class with other documented classes. Explicit enabling a collaboration graph,
+# when COLLABORATION_GRAPH is set to NO, can be accomplished by means of the
+# command \collaborationgraph. Disabling a collaboration graph can be
+# accomplished by means of the command \hidecollaborationgraph.
 # The default value is: YES.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 COLLABORATION_GRAPH    = YES
 
-# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
-# groups, showing the direct groups dependencies.
+# If the GROUP_GRAPHS tag is set to YES then Doxygen will generate a graph for
+# groups, showing the direct groups dependencies. Explicit enabling a group
+# dependency graph, when GROUP_GRAPHS is set to NO, can be accomplished by means
+# of the command \groupgraph. Disabling a directory graph can be accomplished by
+# means of the command \hidegroupgraph. See also the chapter Grouping in the
+# manual.
 # The default value is: YES.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 GROUP_GRAPHS           = YES
 
-# If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
+# If the UML_LOOK tag is set to YES, Doxygen will generate inheritance and
 # collaboration diagrams in a style similar to the OMG's Unified Modeling
 # Language.
 # The default value is: NO.
@@ -2120,10 +2577,32 @@ UML_LOOK               = YES
 # but if the number exceeds 15, the total amount of fields shown is limited to
 # 10.
 # Minimum value: 0, maximum value: 100, default value: 10.
-# This tag requires that the tag HAVE_DOT is set to YES.
+# This tag requires that the tag UML_LOOK is set to YES.
 
 UML_LIMIT_NUM_FIELDS   = 10
 
+# If the DOT_UML_DETAILS tag is set to NO, Doxygen will show attributes and
+# methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS
+# tag is set to YES, Doxygen will add type and arguments for attributes and
+# methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, Doxygen
+# will not generate fields with class member information in the UML graphs. The
+# class diagrams will look similar to the default class diagrams but using UML
+# notation for the relationships.
+# Possible values are: NO, YES and NONE.
+# The default value is: NO.
+# This tag requires that the tag UML_LOOK is set to YES.
+
+DOT_UML_DETAILS        = NO
+
+# The DOT_WRAP_THRESHOLD tag can be used to set the maximum number of characters
+# to display on a single line. If the actual line length exceeds this threshold
+# significantly it will be wrapped across multiple lines. Some heuristics are
+# applied to avoid ugly line breaks.
+# Minimum value: 0, maximum value: 1000, default value: 17.
+# This tag requires that the tag HAVE_DOT is set to YES.
+
+DOT_WRAP_THRESHOLD     = 17
+
 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
 # collaboration graphs will show the relations between templates and their
 # instances.
@@ -2133,69 +2612,88 @@ UML_LIMIT_NUM_FIELDS   = 10
 TEMPLATE_RELATIONS     = NO
 
 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
-# YES then doxygen will generate a graph for each documented file showing the
+# YES then Doxygen will generate a graph for each documented file showing the
 # direct and indirect include dependencies of the file with other documented
-# files.
+# files. Explicit enabling an include graph, when INCLUDE_GRAPH is is set to NO,
+# can be accomplished by means of the command \includegraph. Disabling an
+# include graph can be accomplished by means of the command \hideincludegraph.
 # The default value is: YES.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 INCLUDE_GRAPH          = YES
 
 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
-# set to YES then doxygen will generate a graph for each documented file showing
+# set to YES then Doxygen will generate a graph for each documented file showing
 # the direct and indirect include dependencies of the file with other documented
-# files.
+# files. Explicit enabling an included by graph, when INCLUDED_BY_GRAPH is set
+# to NO, can be accomplished by means of the command \includedbygraph. Disabling
+# an included by graph can be accomplished by means of the command
+# \hideincludedbygraph.
 # The default value is: YES.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 INCLUDED_BY_GRAPH      = YES
 
-# If the CALL_GRAPH tag is set to YES then doxygen will generate a call
+# If the CALL_GRAPH tag is set to YES then Doxygen will generate a call
 # dependency graph for every global function or class method.
 #
 # Note that enabling this option will significantly increase the time of a run.
 # So in most cases it will be better to enable call graphs for selected
-# functions only using the \callgraph command.
+# functions only using the \callgraph command. Disabling a call graph can be
+# accomplished by means of the command \hidecallgraph.
 # The default value is: NO.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 CALL_GRAPH             = YES
 
-# If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
+# If the CALLER_GRAPH tag is set to YES then Doxygen will generate a caller
 # dependency graph for every global function or class method.
 #
 # Note that enabling this option will significantly increase the time of a run.
 # So in most cases it will be better to enable caller graphs for selected
-# functions only using the \callergraph command.
+# functions only using the \callergraph command. Disabling a caller graph can be
+# accomplished by means of the command \hidecallergraph.
 # The default value is: NO.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 CALLER_GRAPH           = YES
 
-# If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
+# If the GRAPHICAL_HIERARCHY tag is set to YES then Doxygen will graphical
 # hierarchy of all classes instead of a textual one.
 # The default value is: YES.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 GRAPHICAL_HIERARCHY    = YES
 
-# If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
+# If the DIRECTORY_GRAPH tag is set to YES then Doxygen will show the
 # dependencies a directory has on other directories in a graphical way. The
 # dependency relations are determined by the #include relations between the
-# files in the directories.
+# files in the directories. Explicit enabling a directory graph, when
+# DIRECTORY_GRAPH is set to NO, can be accomplished by means of the command
+# \directorygraph. Disabling a directory graph can be accomplished by means of
+# the command \hidedirectorygraph.
 # The default value is: YES.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 DIRECTORY_GRAPH        = YES
 
+# The DIR_GRAPH_MAX_DEPTH tag can be used to limit the maximum number of levels
+# of child directories generated in directory dependency graphs by dot.
+# Minimum value: 1, maximum value: 25, default value: 1.
+# This tag requires that the tag DIRECTORY_GRAPH is set to YES.
+
+DIR_GRAPH_MAX_DEPTH    = 1
+
 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
-# generated by dot.
+# generated by dot. For an explanation of the image formats see the section
+# output formats in the documentation of the dot tool (Graphviz (see:
+# https://www.graphviz.org/)).
 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
 # to make the SVG files visible in IE 9+ (other browsers do not have this
 # requirement).
-# Possible values are: png, png:cairo, png:cairo:cairo, png:cairo:gd, png:gd,
-# png:gd:gd, jpg, jpg:cairo, jpg:cairo:gd, jpg:gd, jpg:gd:gd, gif, gif:cairo,
-# gif:cairo:gd, gif:gd, gif:gd:gd and svg.
+# Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,
+# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
+# png:gdiplus:gdiplus.
 # The default value is: png.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
@@ -2226,11 +2724,12 @@ DOT_PATH               =
 
 DOTFILE_DIRS           =
 
-# The MSCFILE_DIRS tag can be used to specify one or more directories that
-# contain msc files that are included in the documentation (see the \mscfile
-# command).
+# You can include diagrams made with dia in Doxygen documentation. Doxygen will
+# then run dia to produce the diagram and insert it in the documentation. The
+# DIA_PATH tag allows you to specify the directory where the dia binary resides.
+# If left empty dia is assumed to be found in the default search path.
 
-MSCFILE_DIRS           =
+DIA_PATH               =
 
 # The DIAFILE_DIRS tag can be used to specify one or more directories that
 # contain dia files that are included in the documentation (see the \diafile
@@ -2238,17 +2737,35 @@ MSCFILE_DIRS           =
 
 DIAFILE_DIRS           =
 
+# When using PlantUML, the PLANTUML_JAR_PATH tag should be used to specify the
+# path where java can find the plantuml.jar file or to the filename of jar file
+# to be used. If left blank, it is assumed PlantUML is not used or called during
+# a preprocessing step. Doxygen will generate a warning when it encounters a
+# \startuml command in this case and will not generate output for the diagram.
+
+PLANTUML_JAR_PATH      =
+
+# When using PlantUML, the PLANTUML_CFG_FILE tag can be used to specify a
+# configuration file for PlantUML.
+
+PLANTUML_CFG_FILE      =
+
+# When using PlantUML, the specified paths are searched for files specified by
+# the !include statement in a PlantUML block.
+
+PLANTUML_INCLUDE_PATH  =
+
 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
 # that will be shown in the graph. If the number of nodes in a graph becomes
-# larger than this value, doxygen will truncate the graph, which is visualized
-# by representing a node as a red box. Note that doxygen if the number of direct
+# larger than this value, Doxygen will truncate the graph, which is visualized
+# by representing a node as a red box. Note that if the number of direct
 # children of the root node in a graph is already larger than
 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
 # Minimum value: 0, maximum value: 10000, default value: 50.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
-DOT_GRAPH_MAX_NODES    = 50
+DOT_GRAPH_MAX_NODES    = 60
 
 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
 # generated by dot. A depth value of 3 means that only nodes reachable from the
@@ -2262,18 +2779,6 @@ DOT_GRAPH_MAX_NODES    = 50
 
 MAX_DOT_GRAPH_DEPTH    = 5
 
-# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
-# background. This is disabled by default, because dot on Windows does not seem
-# to support this out of the box.
-#
-# Warning: Depending on the platform used, enabling this option may lead to
-# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
-# read).
-# The default value is: NO.
-# This tag requires that the tag HAVE_DOT is set to YES.
-
-DOT_TRANSPARENT        = NO
-
 # Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
 # files in one run (i.e. multiple -o and -T options on the command line). This
 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
@@ -2283,17 +2788,37 @@ DOT_TRANSPARENT        = NO
 
 DOT_MULTI_TARGETS      = YES
 
-# If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
+# If the GENERATE_LEGEND tag is set to YES Doxygen will generate a legend page
 # explaining the meaning of the various boxes and arrows in the dot generated
 # graphs.
+# Note: This tag requires that UML_LOOK isn't set, i.e. the Doxygen internal
+# graphical representation for inheritance and collaboration diagrams is used.
 # The default value is: YES.
 # This tag requires that the tag HAVE_DOT is set to YES.
 
 GENERATE_LEGEND        = YES
 
-# If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate dot
+# If the DOT_CLEANUP tag is set to YES, Doxygen will remove the intermediate
 # files that are used to generate the various graphs.
+#
+# Note: This setting is not only used for dot files but also for msc temporary
+# files.
 # The default value is: YES.
-# This tag requires that the tag HAVE_DOT is set to YES.
 
 DOT_CLEANUP            = YES
+
+# You can define message sequence charts within Doxygen comments using the \msc
+# command. If the MSCGEN_TOOL tag is left empty (the default), then Doxygen will
+# use a built-in version of mscgen tool to produce the charts. Alternatively,
+# the MSCGEN_TOOL tag can also specify the name an external tool. For instance,
+# specifying prog as the value, Doxygen will call the tool as prog -T
+# <outfile_format> -o <outputfile> <inputfile>. The external tool should support
+# output file formats "png", "eps", "svg", and "ismap".
+
+MSCGEN_TOOL            =
+
+# The MSCFILE_DIRS tag can be used to specify one or more directories that
+# contain msc files that are included in the documentation (see the \mscfile
+# command).
+
+MSCFILE_DIRS           =
diff --git a/include/helper.h b/include/helper.h
index ed161931f..d85e4737b 100644
--- a/include/helper.h
+++ b/include/helper.h
@@ -396,6 +396,9 @@ char *helper_string_replace_if_exists(char *string, ...);
  * @param ext NULL terminated array of file extension passed to option.
  * @param parent_dir The file that was used to import this file, or NULL.
  *
+ * Get the full path to the theme, trying to resolve it over the possible
+ * locations.
+ *
  * @returns path to theme or copy of filename if not found.
  */
 char *helper_get_theme_path(const char *file, const char **ext,
diff --git a/include/rofi-types.h b/include/rofi-types.h
index 9ca29f565..023e8d2f0 100644
--- a/include/rofi-types.h
+++ b/include/rofi-types.h
@@ -14,8 +14,6 @@ typedef enum {
   P_DOUBLE,
   /** String */
   P_STRING,
-  /** Character */
-  P_CHAR,
   /** Boolean */
   P_BOOLEAN,
   /** Color */
@@ -260,8 +258,6 @@ typedef union _PropertyValue {
   double f;
   /** String */
   char *s;
-  /** Character */
-  char c;
   /** boolean */
   gboolean b;
   /** Color */
diff --git a/lexer/theme-lexer.l b/lexer/theme-lexer.l
index 0a8441583..5af651ca2 100644
--- a/lexer/theme-lexer.l
+++ b/lexer/theme-lexer.l
@@ -186,7 +186,6 @@ WORD_ENV   [[:alpha:]_][[:alnum:]_]*
 COLOR_NAME [[:alpha:]]+
 STRING     \"{UANYN}*\"|\'{UANYN}*\'
 STRING_LIST \"{UANYNP1}*\"|\'{UANYNP2}*\'
-CHAR       \'({ASCN}|\\\\|\\\'|\\0)\'
 HEX        [[:xdigit:]]
 NUMBER     [[:digit:]]+
 UNARYMIN   -
@@ -522,7 +521,6 @@ if ( queue == NULL ) {
 <PROPERTIES,PROPERTIES_ARRAY,PROPERTIES_ENV,PROPERTIES_VAR_DEFAULT,MEDIA_CONTENT>{UNARYMIN}            { return T_MIN; }
 <PROPERTIES,PROPERTIES_ENV,PROPERTIES_VAR_DEFAULT>{STRING}                                             { yytext[yyleng-1] = '\0'; yylval->sval = g_strcompress(&yytext[1]); return T_STRING;}
 <PROPERTIES_ARRAY>{STRING_LIST}                                                                        { yytext[yyleng-1] = '\0'; yylval->sval = g_strcompress(&yytext[1]); return T_STRING;}
-<PROPERTIES,PROPERTIES_ARRAY,PROPERTIES_ENV,PROPERTIES_VAR_DEFAULT>{CHAR}                { yytext[yyleng-1] = '\0'; yylval->cval = g_strcompress(&yytext[1])[0]; return T_CHAR;}
 
 <PROPERTIES,PROPERTIES_ARRAY,PROPERTIES_ENV,PROPERTIES_VAR_DEFAULT>@{WORD}               {
     yylval->sval = g_strdup(yytext+1);
diff --git a/lexer/theme-parser.y b/lexer/theme-parser.y
index 89d24baaf..51fa11bb4 100644
--- a/lexer/theme-parser.y
+++ b/lexer/theme-parser.y
@@ -164,7 +164,6 @@ static ThemeColor hwb_to_rgb ( double h, double w, double b )
 %token <fval>     T_DOUBLE              "Floating-point number"
 %token <sval>     T_STRING              "UTF-8 encode string"
 %token <sval>     T_MEDIA_TYPE          "Media type"
-%token <cval>     T_CHAR                "Character"
 %token <sval>     T_PROP_NAME           "property name"
 %token <colorval> T_COLOR_NAME          "Color value by name"
 %token <sval>     T_NAME_ELEMENT        "Element name"
@@ -567,10 +566,6 @@ t_property_element
         $$ = rofi_theme_property_create ( P_STRING );
         $$->value.s = $1;
     }
-|   T_CHAR {
-        $$ = rofi_theme_property_create ( P_CHAR );
-        $$->value.c = $1;
-    }
 |   T_LINK {
         $$ = rofi_theme_property_create ( P_LINK );
         $$->value.link.name = $1;
diff --git a/meson.build b/meson.build
index e981b4608..63829b406 100644
--- a/meson.build
+++ b/meson.build
@@ -1,5 +1,5 @@
 project('rofi', 'c',
-    version: '1.7.5+wayland3-dev',
+    version: '1.7.7+wayland1',
     meson_version: '>=0.59.0',
     license: [ 'MIT' ],
     default_options: [
diff --git a/mkdocs/docs/1.7.6/rofi-debugging.5.markdown b/mkdocs/docs/1.7.6/rofi-debugging.5.markdown
new file mode 100644
index 000000000..4df15d529
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-debugging.5.markdown
@@ -0,0 +1,177 @@
+# rofi-debugging(5)
+
+## NAME
+
+Debugging rofi.
+
+When reporting an issue with rofi crashing, or misbehaving. It helps to do some
+small test to help pin-point the problem.
+
+First try disabling your custom configuration: `-no-config`
+
+This disables the parsing of the configuration files. This runs rofi in *stock*
+mode.
+
+If you run custom C plugins, you can disable the plugins using: `-no-plugins`
+
+## Get the relevant information for an issue
+
+Please pastebin the output of the following commands:
+
+```bash
+rofi -help
+rofi -dump-config
+rofi -dump-theme
+```
+
+`rofi -help`  provides us with the configuration files parsed, the exact
+version, monitor layout and more useful information.
+
+The `rofi -dump-config` and `rofi -dump-theme` output gives us `rofi`
+interpretation of your configuration and theme.
+
+Please check the output for identifiable information and remove this.
+
+## Timing traces
+
+To get a timing trace, enable the **Timings** debug domain.
+
+```bash
+G_MESSAGES_DEBUG=Timings rofi -show drun
+```
+It will show a trace with (useful) timing information at relevant points during
+the execution. This will help debugging when rofi is slow to start.
+
+Example trace:
+
+```text
+(process:14942): Timings-DEBUG: 13:47:39.335: 0.000000 (0.000000): Started
+(process:14942): Timings-DEBUG: 13:47:39.335: 0.000126 (0.000126): ../source/rofi.c:main:786 
+(process:14942): Timings-DEBUG: 13:47:39.335: 0.000163 (0.000037): ../source/rofi.c:main:819 
+(process:14942): Timings-DEBUG: 13:47:39.336: 0.000219 (0.000056): ../source/rofi.c:main:826 Setup Locale
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001235 (0.001016): ../source/rofi.c:main:828 Collect MODI
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001264 (0.000029): ../source/rofi.c:main:830 Setup MODI
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001283 (0.000019): ../source/rofi.c:main:834 Setup mainloop
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001369 (0.000086): ../source/rofi.c:main:837 NK Bindings
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001512 (0.000143): ../source/xcb.c:display_setup:1177 Open Display
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001829 (0.000317): ../source/xcb.c:display_setup:1192 Setup XCB
+(process:14942): Timings-DEBUG: 13:47:39.346: 0.010650 (0.008821): ../source/rofi.c:main:844 Setup Display
+(process:14942): Timings-DEBUG: 13:47:39.346: 0.010715 (0.000065): ../source/rofi.c:main:848 Setup abe
+(process:14942): Timings-DEBUG: 13:47:39.350: 0.015101 (0.004386): ../source/rofi.c:main:883 Load cmd config 
+(process:14942): Timings-DEBUG: 13:47:39.351: 0.015275 (0.000174): ../source/rofi.c:main:907 Setup Modi
+(process:14942): Timings-DEBUG: 13:47:39.351: 0.015291 (0.000016): ../source/view.c:rofi_view_workers_initialize:1922 Setup Threadpool, start
+(process:14942): Timings-DEBUG: 13:47:39.351: 0.015349 (0.000058): ../source/view.c:rofi_view_workers_initialize:1945 Setup Threadpool, done
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032018 (0.016669): ../source/rofi.c:main:1000 Setup late Display
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032080 (0.000062): ../source/rofi.c:main:1003 Theme setup
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032109 (0.000029): ../source/rofi.c:startup:668 Startup
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032121 (0.000012): ../source/rofi.c:startup:677 Grab keyboard
+(process:14942): Timings-DEBUG: 13:47:39.368: 0.032214 (0.000093): ../source/view.c:__create_window:701 xcb create window
+(process:14942): Timings-DEBUG: 13:47:39.368: 0.032235 (0.000021): ../source/view.c:__create_window:705 xcb create gc
+(process:14942): Timings-DEBUG: 13:47:39.368: 0.033136 (0.000901): ../source/view.c:__create_window:714 create cairo surface
+(process:14942): Timings-DEBUG: 13:47:39.369: 0.033286 (0.000150): ../source/view.c:__create_window:723 pango cairo font setup
+(process:14942): Timings-DEBUG: 13:47:39.369: 0.033351 (0.000065): ../source/view.c:__create_window:761 configure font
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045896 (0.012545): ../source/view.c:__create_window:769 textbox setup
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045944 (0.000048): ../source/view.c:__create_window:781 setup window attributes
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045955 (0.000011): ../source/view.c:__create_window:791 setup window fullscreen
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045966 (0.000011): ../source/view.c:__create_window:797 setup window name and class
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045974 (0.000008): ../source/view.c:__create_window:808 setup startup notification
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045981 (0.000007): ../source/view.c:__create_window:810 done
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045992 (0.000011): ../source/rofi.c:startup:679 Create Window
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045999 (0.000007): ../source/rofi.c:startup:681 Parse ABE
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.046113 (0.000114): ../source/rofi.c:startup:684 Config sanity check
+(process:14942): Timings-DEBUG: 13:47:39.384: 0.048229 (0.002116): ../source/dialogs/run.c:get_apps:216 start
+(process:14942): Timings-DEBUG: 13:47:39.390: 0.054626 (0.006397): ../source/dialogs/run.c:get_apps:336 stop
+(process:14942): Timings-DEBUG: 13:47:39.390: 0.054781 (0.000155): ../source/dialogs/drun.c:get_apps:634 Get Desktop apps (start)
+(process:14942): Timings-DEBUG: 13:47:39.391: 0.055264 (0.000483): ../source/dialogs/drun.c:get_apps:641 Get Desktop apps (user dir)
+(process:14942): Timings-DEBUG: 13:47:39.418: 0.082884 (0.027620): ../source/dialogs/drun.c:get_apps:659 Get Desktop apps (system dirs)
+(process:14942): Timings-DEBUG: 13:47:39.418: 0.082944 (0.000060): ../source/dialogs/drun.c:get_apps_history:597 Start drun history
+(process:14942): Timings-DEBUG: 13:47:39.418: 0.082977 (0.000033): ../source/dialogs/drun.c:get_apps_history:617 Stop drun history
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083638 (0.000661): ../source/dialogs/drun.c:get_apps:664 Sorting done.
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083685 (0.000047): ../source/view.c:rofi_view_create:1759 
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083700 (0.000015): ../source/view.c:rofi_view_create:1783 Startup notification
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083711 (0.000011): ../source/view.c:rofi_view_create:1786 Get active monitor
+(process:14942): Timings-DEBUG: 13:47:39.420: 0.084693 (0.000982): ../source/view.c:rofi_view_refilter:1028 Filter start
+(process:14942): Timings-DEBUG: 13:47:39.421: 0.085992 (0.001299): ../source/view.c:rofi_view_refilter:1132 Filter done
+(process:14942): Timings-DEBUG: 13:47:39.421: 0.086090 (0.000098): ../source/view.c:rofi_view_update:982 
+(process:14942): Timings-DEBUG: 13:47:39.421: 0.086123 (0.000033): ../source/view.c:rofi_view_update:1002 Background
+(process:14942): Timings-DEBUG: 13:47:39.428: 0.092864 (0.006741): ../source/view.c:rofi_view_update:1008 widgets
+```
+
+## Debug domains
+
+To further debug the plugin, you can get a trace with (lots of) debug
+information. This debug output can be enabled for multiple parts in rofi using
+the glib debug framework. Debug domains can be enabled by setting the
+G\_MESSAGES\_DEBUG environment variable. At the time of creation of this page,
+the following debug domains exist:
+
+- all: Show debug information from all domains.
+- X11Helper: The X11 Helper functions.
+- View: The main window view functions.
+- Widgets.Box: The Box widget.
+- Modes.DMenu: The dmenu mode.
+- Modes.Run: The run mode.
+- Modes.DRun: The desktop file run mode.
+- Modes.Window: The window mode.
+- Modes.Script: The script mode.
+- Modes.Combi: The script mode.
+- Modes.Ssh: The ssh mode.
+- Rofi: The main application.
+- Timings: Get timing output.
+- Theme: Theme engine debug output. (warning lots of output).
+- Widgets.Icon: The Icon widget.
+- Widgets.Box: The box widget.
+- Widgets.Container: The container widget.
+- Widgets.Window: The window widget.
+- Helpers.IconFetcher: Information about icon lookup.
+
+For full list see `man rofi`.
+
+Example: `G_MESSAGES_DEBUG=Dialogs.DRun rofi -show drun` To get specific output
+from the Desktop file run dialog.
+
+To redirect the debug output to a file (`~/rofi.log`) add:
+
+```bash
+rofi -show drun -log ~/rofi.log
+```
+
+Specifying the logfile automatically enabled all log domains.
+This can be useful when rofi is launched from a window manager.
+
+## Creating a backtrace
+
+First make sure you compile **rofi** with debug symbols:
+
+```bash
+make CFLAGS="-O0 -g3" clean rofi
+```
+
+Getting a backtrace using GDB is not very handy. Because if rofi get stuck, it
+grabs keyboard and mouse. So if it crashes in GDB you are stuck. The best way
+to go is to enable core file. (ulimit -c unlimited in bash) then make rofi
+crash. You can then load the core in GDB.
+
+```bash
+gdb rofi core
+```
+
+Then type inside gdb:
+
+```bash
+thread apply all bt
+```
+
+The output trace is useful when reporting crashes.
+
+Some distribution have `systemd-coredump`, this way you can easily get a
+backtrace via `coredumpctl`.
+
+## SEE ALSO
+
+rofi-sensible-terminal(1), dmenu(1), rofi-theme(5),
+rofi-script(5), rofi-keys(5),rofi-theme-selector(1)
+
+## AUTHOR
+
+* Qball Cow <qball@blame.services>
diff --git a/mkdocs/docs/1.7.6/rofi-dmenu.5.markdown b/mkdocs/docs/1.7.6/rofi-dmenu.5.markdown
new file mode 100644
index 000000000..27e484b3f
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-dmenu.5.markdown
@@ -0,0 +1,245 @@
+# rofi-dmenu(5)
+
+## NAME
+
+**rofi dmenu mode** - Rofi dmenu emulation
+
+## DESCRIPTION
+
+To integrate **rofi** into scripts as simple selection dialogs, 
+**rofi** supports emulating **dmenu(1)** (A dynamic menu for X11).
+
+The website for `dmenu` can be found [here](http://tools.suckless.org/dmenu/).
+
+**rofi** does not aim to be 100% compatible with `dmenu`. There are simply too
+many flavors of `dmenu`. The idea is that the basic usage command-line flags
+are obeyed, theme-related flags are not. Besides, **rofi** offers some extended
+features (like multi-select, highlighting, message bar, extra key bindings).
+
+## BASIC CONCEPT
+
+In `dmenu` mode, **rofi** reads data from standard in, splits them into
+separate entries and displays them. If the user selects a row, this is printed
+out to standard out, allowing the script to process it further.
+
+By default separation of rows is done on new lines, making it easy to pipe the
+output a one application into **rofi** and the output of rofi into the next.
+
+## USAGE 
+
+By launching **rofi** with the `-dmenu` flag it will go into dmenu emulation
+mode.
+
+```bash
+ls | rofi -dmenu
+```
+
+### DMENU DROP-IN REPLACEMENT
+
+If `argv[0]` (calling command) is dmenu, **rofi** will start in dmenu mode.
+This way, it can be used as a drop-in replacement for dmenu. Just copy or
+symlink **rofi** to dmenu in `$PATH`.
+
+```bash
+ln -s /usr/bin/rofi /usr/bin/dmenu
+```
+
+### DMENU VS SCRIPT MODE
+
+Script mode is used to extend **rofi**, dmenu mode is used to extend a script.
+The two do share much of the same input format. Please see the
+**rofi-script(5)** manpage for more information.
+
+### DMENU SPECIFIC COMMANDLINE FLAGS
+
+A lot of these options can also be modified by the script using special input.
+See the **rofi-script(5)** manpage for more information about this syntax.
+
+`-sep` *separator*
+
+Separator for `dmenu`. Example: To show a list of 'a' to 'e' with '|' as a
+separator:
+
+```bash
+echo "a|b|c|d|e" | rofi -sep '|' -dmenu
+```
+
+`-p` *prompt*
+
+Specify the prompt to show in `dmenu` mode. For example, select 'monkey',
+a,b,c,d, or e.
+
+```bash
+echo "a|b|c|d|e" | rofi -sep '|' -dmenu -p "monkey"
+```
+
+Default: *dmenu*
+
+`-l` *number of lines to show*
+
+Maximum number of lines the menu may show before scrolling.
+
+```bash
+rofi -dmenu -l 25
+```
+
+Default: *15*
+
+`-i`
+
+Makes `dmenu` searches case-insensitive
+
+`-a` *X*
+
+Active row, mark *X* as active. Where *X* is a comma-separated list of
+python(1)-style indices and ranges, e.g.  indices start at 0, -1 refers to the
+last row with -2 preceding it, ranges are left-open and right-close, and so on.
+You can specify:
+
+- A single row: '5'
+- A range of (last 3) rows: '-3:'
+- 4 rows starting from row 7: '7:11' (or in legacy notation: '7-10')
+- A set of rows: '2,0,-9'
+- Or any combination: '5,-3:,7:11,2,0,-9'
+
+`-u` *X*
+
+Urgent row, mark *X* as urgent. See `-a` option for details.
+
+`-only-match`
+
+Only return a selected item, do not allow custom entry.
+This mode always returns an entry. It will not return if no matching entry is
+selected.
+
+`-no-custom`
+
+Only return a selected item, do not allow custom entry.
+This mode returns directly when no entries given.
+
+`-format` *format*
+
+Allows the output of dmenu to be customized (N is the total number of input
+entries):
+
+- 's' selected string
+- 'i' index (0 - (N-1))
+- 'd' index (1 - N)
+- 'q' quote string
+- 'p' Selected string stripped from Pango markup (Needs to be a valid string)
+- 'f' filter string (user input)
+- 'F' quoted filter string (user input)
+
+Default: 's'
+
+`-select` *string*
+
+Select first line that matches the given string
+
+`-mesg` *string*
+
+Add a message line below the filter entry box. Supports Pango markup. For more
+information on supported markup, see
+[here](https://docs.gtk.org/Pango/pango_markup.html)
+
+`-dump`
+
+Dump the filtered list to stdout and quit.
+This can be used to get the list as **rofi** would filter it.
+Use together with `-filter` command.
+
+`-input` *file*
+
+Reads from *file* instead of stdin.
+
+`-password`
+
+Hide the input text. This should not be considered secure!
+
+`-markup-rows`
+
+Tell **rofi** that DMenu input is Pango markup encoded, and should be rendered.
+See [here](https://developer.gnome.org/pygtk/stable/pango-markup-language.html)
+for details about Pango markup.
+
+`-multi-select`
+
+Allow multiple lines to be selected. Adds a small selection indicator to the
+left of each entry.
+
+`-sync`
+
+Force **rofi** mode to first read all data from stdin before showing the
+selection window. This is original dmenu behavior.
+
+Note: the default asynchronous mode will also be automatically disabled if used
+with conflicting options,
+such as `-dump`, `-only-match` or `-auto-select`.
+
+`-window-title` *title*
+
+Set name used for the window title. Will be shown as Rofi - *title*
+
+`-w` *windowid*
+
+Position **rofi** over the window with the given X11 window ID.
+
+`-keep-right`
+
+Set ellipsize mode to start. So, the end of the string is visible.
+
+`-display-columns`
+
+A comma seperated list of columns to show.
+
+`-display-column-separator`
+
+The column separator. This is a regex. 
+
+*default*: '\t'
+
+`-ballot-selected-str` *string*
+
+When multi-select is enabled, prefix this string when element is selected.
+
+*default*: "☑ "
+
+`-ballot-unselected-str` *string*
+
+When multi-select is enabled, prefix this string when element is not selected.
+
+*default*: "☐ "
+
+`-ellipsize-mode` (start|middle|end)
+
+Set ellipsize mode on the listview.
+
+*default* "end"
+
+## PARSING ROW OPTIONS
+
+Extra options for individual rows can be also set. See the **rofi-script(5)**
+manpage for details; the syntax and supported features are identical.
+
+## RETURN VALUE
+
+- **0**: Row has been selected accepted by user.
+- **1**: User cancelled the selection.
+- **10-28**: Row accepted by custom keybinding.
+
+## SEE ALSO
+
+rofi(1), rofi-sensible-terminal(1), dmenu(1), rofi-theme(5), rofi-script(5),
+rofi-theme-selector(1), ascii(7)
+
+## AUTHOR
+
+Qball Cow <qball@gmpclient.org>
+
+Rasmus Steinke <rasi@xssn.at>
+
+Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: Sean Pringle <sean.pringle@gmail.com>
+
+For a full list of authors, check the AUTHORS file.
diff --git a/mkdocs/docs/1.7.6/rofi-keys.5.markdown b/mkdocs/docs/1.7.6/rofi-keys.5.markdown
new file mode 100644
index 000000000..8aeefacc2
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-keys.5.markdown
@@ -0,0 +1,576 @@
+# rofi-keys(5)
+
+## NAME
+
+**rofi keys** - Rofi Key and Mouse bindings
+
+## DESCRIPTION
+
+**rofi** supports overriding of any of it key and mouse binding.
+
+## Setting binding
+
+Bindings can be done on the commandline (-{bindingname}):
+
+```bash
+rofi -show run -kb-accept-entry 'Control+Shift+space'
+```
+
+or via the configuration file:
+
+```css
+configuration {
+  kb-accept-entry: "Control+Shift+space";
+}
+```
+
+The key can be set by its name (see above) or its keycode:
+
+```css
+configuration {
+  kb-accept-entry: "Control+Shift+[65]";
+}
+```
+
+An easy way to look up keycode is xev(1).
+
+Multiple keys can be specified for an action as a comma separated list:
+
+```css
+configuration {
+  kb-accept-entry: "Control+Shift+space,Return";
+}
+```
+
+By Default **rofi** reacts on pressing, to act on the release of all keys
+prepend the binding with `!`:
+
+```css
+configuration {
+  kb-accept-entry: "!Control+Shift+space,Return";
+}
+```
+
+## Unsetting a binding
+
+To unset a binding, pass an empty string.
+
+```css
+configuration {
+  kb-clear-line: "";
+}
+```
+
+## Keyboard Bindings
+
+`kb-primary-paste`
+
+Paste primary selection
+
+Default:  Control+V,Shift+Insert
+
+`kb-secondary-paste`
+
+Paste clipboard
+
+Default:  Control+v,Insert
+
+`kb-secondary-copy`
+
+Copy current selection to clipboard
+
+Default:  Control+c
+
+`kb-clear-line`
+
+Clear input line
+
+Default:  Control+w
+
+`kb-move-front`
+
+Beginning of line
+
+Default:  Control+a
+
+`kb-move-end`
+
+End of line
+
+Default:  Control+e
+
+`kb-move-word-back`
+
+Move back one word
+
+Default:  Alt+b,Control+Left
+
+`kb-move-word-forward`
+
+Move forward one word
+
+Default:  Alt+f,Control+Right
+
+`kb-move-char-back`
+
+Move back one char
+
+Default:  Left,Control+b
+
+`kb-move-char-forward`
+
+Move forward one char
+
+Default:  Right,Control+f
+
+`kb-remove-word-back`
+
+Delete previous word
+
+Default:  Control+Alt+h,Control+BackSpace
+
+`kb-remove-word-forward`
+
+Delete next word
+
+Default:  Control+Alt+d
+
+`kb-remove-char-forward`
+
+Delete next char
+
+Default:  Delete,Control+d
+
+`kb-remove-char-back`
+
+Delete previous char
+
+Default:  BackSpace,Shift+BackSpace,Control+h
+
+`kb-remove-to-eol`
+
+Delete till the end of line
+
+Default:  Control+k
+
+`kb-remove-to-sol`
+
+Delete till the start of line
+
+Default:  Control+u
+
+`kb-accept-entry`
+
+Accept entry
+
+Default:  Control+j,Control+m,Return,KP\_Enter
+
+`kb-accept-custom`
+
+Use entered text as command (in ssh/run modes)
+
+Default:  Control+Return
+
+`kb-accept-custom-alt`
+
+Use entered text as command (in ssh/run modes)
+
+Default:  Control+Shift+Return
+
+`kb-accept-alt`
+
+Use alternate accept command.
+
+Default:  Shift+Return
+
+`kb-delete-entry`
+
+Delete entry from history
+
+Default:  Shift+Delete
+
+`kb-mode-next`
+
+Switch to the next mode.
+
+Default:  Shift+Right,Control+Tab
+
+`kb-mode-previous`
+
+Switch to the previous mode.
+
+Default:  Shift+Left,Control+ISO\_Left\_Tab
+
+`kb-mode-complete`
+
+Start completion for mode.
+
+Default:  Control+l
+
+`kb-row-left`
+
+Go to the previous column
+
+Default:  Control+Page\_Up
+
+`kb-row-right`
+
+Go to the next column
+
+Default:  Control+Page\_Down
+
+`kb-row-up`
+
+Select previous entry
+
+Default:  Up,Control+p
+
+`kb-row-down`
+
+Select next entry
+
+Default:  Down,Control+n
+
+`kb-row-tab`
+
+Go to next row, if one left, accept it, if no left next mode.
+
+Default:
+
+`kb-element-next`
+
+Go to next row.
+
+Default: Tab
+
+`kb-element-prev`
+
+Go to previous row.
+
+Default: ISO\_Left\_Tab
+
+`kb-page-prev`
+
+Go to the previous page
+
+Default:  Page\_Up
+
+`kb-page-next`
+
+Go to the next page
+
+Default:  Page\_Down
+
+`kb-row-first`
+
+Go to the first entry
+
+Default:  Home,KP\_Home
+
+`kb-row-last`
+
+Go to the last entry
+
+Default:  End,KP\_End
+
+`kb-row-select`
+
+Set selected item as input text
+
+Default:  Control+space
+
+`kb-screenshot`
+
+Take a screenshot of the rofi window
+
+Default:  Alt+S
+
+`kb-ellipsize`
+
+Toggle between ellipsize modes for displayed data
+
+Default:  Alt+period
+
+`kb-toggle-case-sensitivity`
+
+Toggle case sensitivity
+
+Default:  grave,dead\_grave
+
+`kb-toggle-sort`
+
+Toggle filtered menu sort
+
+Default:  Alt+grave
+
+`kb-cancel`
+
+Quit rofi
+
+Default:  Escape,Control+g,Control+bracketleft
+
+`kb-custom-1`
+
+Custom keybinding 1
+
+Default:  Alt+1
+
+`kb-custom-2`
+
+Custom keybinding 2
+
+Default:  Alt+2
+
+`kb-custom-3`
+
+Custom keybinding 3
+
+Default:  Alt+3
+
+`kb-custom-4`
+
+Custom keybinding 4
+
+Default:  Alt+4
+
+`kb-custom-5`
+
+Custom Keybinding 5
+
+Default:  Alt+5
+
+`kb-custom-6`
+
+Custom keybinding 6
+
+Default:  Alt+6
+
+`kb-custom-7`
+
+Custom Keybinding 7
+
+Default:  Alt+7
+
+`kb-custom-8`
+
+Custom keybinding 8
+
+Default:  Alt+8
+
+`kb-custom-9`
+
+Custom keybinding 9
+
+Default:  Alt+9
+
+`kb-custom-10`
+
+Custom keybinding 10
+
+Default:  Alt+0
+
+`kb-custom-11`
+
+Custom keybinding 11
+
+Default:  Alt+exclam
+
+`kb-custom-12`
+
+Custom keybinding 12
+
+Default:  Alt+at
+
+`kb-custom-13`
+
+Custom keybinding 13
+
+Default:  Alt+numbersign
+
+`kb-custom-14`
+
+Custom keybinding 14
+
+Default:  Alt+dollar
+
+`kb-custom-15`
+
+Custom keybinding 15
+
+Default:  Alt+percent
+
+`kb-custom-16`
+
+Custom keybinding 16
+
+Default:  Alt+dead\_circumflex
+
+`kb-custom-17`
+
+Custom keybinding 17
+
+Default:  Alt+ampersand
+
+`kb-custom-18`
+
+Custom keybinding 18
+
+Default:  Alt+asterisk
+
+`kb-custom-19`
+
+Custom Keybinding 19
+
+Default:  Alt+parenleft
+
+`kb-select-1`
+
+Select row 1
+
+Default:  Super+1
+
+`kb-select-2`
+
+Select row 2
+
+Default:  Super+2
+
+`kb-select-3`
+
+Select row 3
+
+Default:  Super+3
+
+`kb-select-4`
+
+Select row 4
+
+Default:  Super+4
+
+`kb-select-5`
+
+Select row 5
+
+Default:  Super+5
+
+`kb-select-6`
+
+Select row 6
+
+Default:  Super+6
+
+`kb-select-7`
+
+Select row 7
+
+Default:  Super+7
+
+`kb-select-8`
+
+Select row 8
+
+Default:  Super+8
+
+`kb-select-9`
+
+Select row 9
+
+Default:  Super+9
+
+`kb-select-10`
+
+Select row 10
+
+Default:  Super+0
+
+`kb-entry-history-up`
+
+Go up in the entry history.
+
+Default:    Control+Up
+
+`kb-entry-history-down`
+
+Go down in the entry history.
+
+Default:    Control+Down
+
+## Mouse Bindings
+
+`ml-row-left`
+
+Go to the previous column
+
+Default:  ScrollLeft
+
+`ml-row-right`
+
+Go to the next column
+
+Default:  ScrollRight
+
+`ml-row-up`
+
+Select previous entry
+
+Default:  ScrollUp
+
+`ml-row-down`
+
+Select next entry
+
+Default:  ScrollDown
+
+`me-select-entry`
+
+Select hovered row
+
+Default:  MousePrimary
+
+`me-accept-entry`
+
+Accept hovered row
+
+Default:  MouseDPrimary
+
+`me-accept-custom`
+
+Accept hovered row with custom action
+
+Default:  Control+MouseDPrimary
+
+## Mouse key bindings
+
+The following mouse buttons can be bound:
+
+* `Primary`: Primary (Left) mouse button click.
+* `Secondary`:  Secondary (Right) mouse button click.
+* `Middle`: Middle mouse button click.
+* `Forward`: The forward mouse button.
+* `Back`: The back mouse button.
+* `ExtraN`: The N'the mouse button. (Depending on mouse support).
+
+The Identifier is constructed as follow:
+
+`Mouse<D><Button>`
+
+* `D` indicates optional Double press.
+* `Button` is the button name.
+
+So `MouseDPrimary` is Primary (`Left`) mouse button double click.
+
+## SEE ALSO
+
+rofi(1), rofi-sensible-terminal(1), rofi-theme(5), rofi-script(5)
+
+## AUTHOR
+
+Qball Cow <qball@gmpclient.org>
+
+Rasmus Steinke <rasi@xssn.at>
+
+Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: Sean Pringle <sean.pringle@gmail.com>
+
+For a full list of authors, check the AUTHORS file.
diff --git a/mkdocs/docs/1.7.6/rofi-script.5.markdown b/mkdocs/docs/1.7.6/rofi-script.5.markdown
new file mode 100644
index 000000000..aeeac8fda
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-script.5.markdown
@@ -0,0 +1,216 @@
+# rofi-script(5)
+
+## NAME
+
+**rofi script mode** - Rofi format for scriptable mode.
+
+## DESCRIPTION
+
+**rofi** supports modes that use simple scripts in the background to generate a
+list and process the result from user actions.  This provide a simple interface
+to make simple extensions to rofi.
+
+## USAGE
+
+To specify a script mode, set a mode with the following syntax:
+"{name}:{executable}"
+
+For example:
+
+```bash
+rofi -show fb -modes "fb:file_browser.sh"
+```
+
+The name should be unique.
+
+## API
+
+Rofi calls the executable without arguments on startup.  This should generate a
+list of options, separated by a newline (`\n`) (This can be changed by the
+script). If the user selects an option, rofi calls the executable with the text
+of that option as the first argument. If the script returns no entries, rofi
+quits.
+
+A simple script would be:
+
+```bash
+#!/usr/bin/env bash
+
+if [ x"$@" = x"quit" ]
+then
+    exit 0
+fi
+echo "reload"
+echo "quit"
+
+```
+
+This shows two entries, reload and quit. When the quit entry is selected, rofi
+closes.
+
+## Environment
+
+Rofi sets the following environment variable when executing the script:
+
+### `ROFI_RETV`
+
+An integer number with the current state:
+
+- **0**: Initial call of script.
+- **1**: Selected an entry.
+- **2**: Selected a custom entry.
+- **10-28**: Custom keybinding 1-19 ( need to be explicitly enabled by script ).
+
+### `ROFI_INFO`
+
+Environment get set when selected entry get set with the property value of the
+'info' row option, if set.
+
+### `ROFI_DATA`
+
+Environment get set when script sets `data` option in header.
+
+## Passing mode options
+
+Extra options, like setting the prompt, can be set by the script. Extra options
+are lines that start with a NULL character (`\0`) followed by a key, separator
+(`\x1f`) and value.
+
+For example to set the prompt:
+
+```bash
+    echo -en "\0prompt\x1fChange prompt\n"
+```
+
+The following extra options exists:
+
+-   **prompt**:      Update the prompt text.
+
+-   **message**:     Update the message text.
+
+-   **markup-rows**: If 'true' renders markup in the row.
+
+-   **urgent**:      Mark rows as urgent. (for syntax see the urgent option in
+    dmenu mode)
+
+-   **active**:      Mark rows as active. (for syntax see the active option in
+    dmenu mode)
+
+-   **delim**:       Set the delimiter for for next rows. Default is '\n' and
+    this option should finish with this. Only call this on first call of script,
+    it is remembered for consecutive calls.
+
+-   **no-custom**:   If set to 'true'; only accept listed entries, ignore custom
+    input.
+
+-   **use-hot-keys**: If set to true, it enabled the Custom keybindings for
+    script. Warning this breaks the normal rofi flow.
+
+-   **keep-selection**: If set, the selection is not moved to the first entry,
+    but the current position is maintained. The filter is cleared.
+
+-   **keep-filter**: If set, the filter is not cleared. 
+
+-   **new-selection**: If `keep-selection` is set, this allows you to override
+    the selected entry (absolute position).
+
+-   **data**:         Passed data to the next execution of the script via
+    **ROFI\_DATA**.
+
+-   **theme**:       Small theme snippet to f.e. change the background color of
+    a widget.
+
+The **theme** property cannot change the interface while running, it is only
+usable for small changes in, for example background color, of widgets that get
+updated during display like the row color of the listview.
+
+## Parsing row options
+
+Extra options for individual rows can be set. The extra option can be specified
+following the same syntax as mode option, but following the entry.
+
+For example:
+
+```bash
+    echo -en "aap\0icon\x1ffolder\n"
+```
+
+The following options are supported:
+
+-   **icon**: Set the icon for that row.
+
+-   **display**: Replace the displayed string. (Original string will still be used for filtering)
+
+-   **meta**: Specify invisible search terms used for filtering.
+
+-   **nonselectable**: If true the row cannot activated.
+
+-   **permanent**: If true the row always shows, independent of filter.
+
+-   **info**: Info that, on selection, gets placed in the `ROFI_INFO`
+    environment variable. This entry does not get searched for filtering.
+
+-   **urgent**: Set urgent flag on entry (true/false)
+
+-   **active**: Set active flag on entry (true/false)
+
+multiple entries can be passed using the `\x1f` separator.
+
+```bash
+    echo -en "aap\0icon\x1ffolder\x1finfo\x1ftest\n"
+```
+
+## Executing external program
+
+If you want to launch an external program from the script, you need to make
+sure it is launched in the background. If not rofi will wait for its output (to
+display).
+
+In bash the best way to do this is using `coproc`.
+
+```bash
+ coproc ( myApp  > /dev/null  2>&1 )
+```
+
+## DASH shell
+
+If you use the `dash` shell for your script, take special care with how dash
+handles escaped values for the separators. See issue #1201 on github.
+
+## Script locations
+
+To specify a script there are the following options:
+
+- Specify an absolute path to the script.
+- The script is executable and located in your $PATH
+
+Scripts located in the following location are **loaded** on startup
+and can be directly launched based on the filename (without extension):
+
+- The script is in `$XDG_CONFIG_HOME/rofi/scripts/`, this is usually
+  `~/.config/rofi/scripts/`.
+
+If you have a script 'mymode.sh' in this folder you can open it using:
+
+```bash
+rofi -show mymode
+```
+
+See `rofi -h` output for a list of detected scripts.
+
+## SEE ALSO
+
+rofi(1), rofi-sensible-terminal(1), dmenu(1), rofi-theme(5),
+rofi-theme-selector(1)
+
+## AUTHOR
+
+Qball Cow <qball@gmpclient.org>
+
+Rasmus Steinke <rasi@xssn.at>
+
+Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: Sean Pringle <sean.pringle@gmail.com>
+
+For a full list of authors, check the AUTHORS file.
diff --git a/mkdocs/docs/1.7.6/rofi-sensible-terminal.1.markdown b/mkdocs/docs/1.7.6/rofi-sensible-terminal.1.markdown
new file mode 100644
index 000000000..1406299dd
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-sensible-terminal.1.markdown
@@ -0,0 +1,50 @@
+# rofi-sensible-terminal(1)
+
+## NAME
+
+**rofi-sensible-terminal** -  launches $TERMINAL with fallbacks
+
+## SYNOPSIS
+
+rofi-sensible-terminal [arguments]
+
+## DESCRIPTION
+
+rofi-sensible-terminal is invoked in the rofi default config to start a terminal. This
+wrapper script is necessary since there is no distribution-independent terminal launcher
+(but for example Debian has x-terminal-emulator). Distribution packagers are responsible for
+shipping this script in a way which is appropriate for the distribution.
+
+It tries to start one of the following (in that order):
+
+* `$TERMINAL` (this is a non-standard variable)
+* x-terminal-emulator
+* urxvt
+* rxvt
+* st
+* terminology
+* qterminal
+* Eterm
+* aterm
+* uxterm
+* xterm
+* roxterm
+* xfce4-terminal.wrapper
+* mate-terminal
+* lxterminal
+* konsole
+* alacritty
+* kitty
+* wezterm
+
+
+## SEE ALSO
+
+rofi(1)
+
+## AUTHORS
+
+Dave Davenport and contributors
+
+Copied script from i3:
+Michael Stapelberg and contributors
diff --git a/mkdocs/docs/1.7.6/rofi-theme-selector.1.markdown b/mkdocs/docs/1.7.6/rofi-theme-selector.1.markdown
new file mode 100644
index 000000000..1fa8b6fe7
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-theme-selector.1.markdown
@@ -0,0 +1,40 @@
+# rofi-theme-selector(1)
+
+## NAME
+
+**rofi-theme-selector** - Preview and apply themes for **rofi**
+
+## DESCRIPTION
+
+**rofi-theme-selector** is a bash/rofi script to preview and apply themes for
+**rofi**. It's part of any installation of **rofi**.
+
+## USAGE
+
+### Running rofi-theme-selector
+
+**rofi-theme-selector** shows a list of all available themes in a **rofi**
+window. It lets you preview each theme with the Enter key and apply the theme
+to your **rofi** configuration file with Alt+a.
+
+## Theme directories
+
+**rofi-theme-selector** searches the following directories for themes:
+
+- ${PREFIX}/share/rofi/themes
+- $XDG_CONFIG_HOME/rofi/themes
+- $XDG_DATA_HOME/share/rofi/themes
+
+${PREFIX} reflects the install location of rofi. In most cases this will be
+"/usr".<br>
+$XDG_CONFIG_HOME is normally unset. Default path is "$HOME/.config".<br>
+$XDG_DATA_HOME is normally unset. Default path is "$HOME/.local/share".
+
+## SEE ALSO
+
+rofi(1)
+
+## AUTHORS
+
+Qball Cow qball@gmpclient.org<br>
+Rasmus Steinke rasi@xssn.at
diff --git a/mkdocs/docs/1.7.6/rofi-theme.5.markdown b/mkdocs/docs/1.7.6/rofi-theme.5.markdown
new file mode 100644
index 000000000..90a273f19
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-theme.5.markdown
@@ -0,0 +1,1660 @@
+# rofi-theme(5)
+
+## NAME
+
+**rofi-theme** - Rofi theme format files
+
+## Getting started with theming
+
+The easiest way to get started theming rofi is by modifying your existing theme.
+
+Themes can be modified/tweaked by adding theming elements to the end of the\
+config file. The default location of this file is `~/.config/rofi/config.rasi`,
+if the file does not exists, you can create it.
+
+A basic config:
+
+```css
+configuration {
+  modes: [ combi ];
+  combi-modes: [ window, drun, run ];
+}
+
+@theme "gruvbox-light"
+ 
+/* Insert theme modifications after this */
+```
+
+For example if we want to change the `Type to filter` text in the entry box we
+append the following:
+
+```css
+entry {
+    placeholder: "Type here";
+}
+```
+
+In the above section, `entry` indicates the widget, `placeholder` is the
+property we want to modify and we set it to the string `"Type here"`. To find
+the commonly available widgets in rofi, see the 'Basic structure' section.
+
+To change the mouse over cursor to a pointer, add:
+
+```css
+entry {
+    placeholder: "Type here";
+    cursor: pointer;
+}
+```
+
+For the next modification, we want to add the icon after each text element and
+increase the size. First we start by modifying the `element` widget:
+
+```css
+
+element {
+  orientation: horizontal;
+  children: [ element-text, element-icon ];
+  spacing: 5px;
+}
+
+```
+
+Resulting in the following packing:
+
+```text
+┌─────────────────────────────────────────────────────────────────────┐ 
+│ element                                                             │ 
+│ ┌─────────────────────────────────────────────┐ ┌─────────────────┐ │ 
+│ │element─text                                 │ │ element─icon    │ │ 
+│ └─────────────────────────────────────────────┘ └─────────────────┘ │ 
+└─────────────────────────────────────────────────────────────────────┘ 
+```
+
+The `element` (container) widget hold each entry in the `listview`, we add the
+two pre-defined children in the order we want to show. We also specify the
+packing direction (`orientation`) and the spacing between the children
+(`spacing`). We specify the space between the two children in absolute pixels
+(`px`).
+
+To increase the icon-size, we need to modify the `element-icon` widget.
+
+```css
+element-icon {
+    size: 2.5em;
+}
+```
+
+```text
+┌─────────────────────────────────────────────────────────────────────┐ 
+│ element                                                             │ 
+│ ┌─────────────────────────────────────────────┐ ┌─────────────────┐ │ 
+│ │element─text                                 │ │    element      │ │ 
+│ │                                             │ │       ─         │ │ 
+│ │                                             │ │     icon        │ │ 
+│ └─────────────────────────────────────────────┘ └─────────────────┘ │ 
+└─────────────────────────────────────────────────────────────────────┘ 
+```
+
+In this example we specify the size in the [em](https://www.w3.org/Style/LieBos3e/em) unit.
+
+Now lets change the text color of both the `entry` and the `element-text`
+widget to red and background to blue.
+
+```css
+entry, element-text {
+  text-color: red;
+  background-color: rgb(0,0,255);
+}
+```
+
+Here we use two different methods of writing down the color, for `text-color`
+we used a named color, for `background-color` we specify it in `rgb`.
+We also specify the property for multiple widgets by passing a comma separated
+list of widget names.
+
+If you want to center the text relative to the icon, we can set this:
+
+```css
+element-text {
+    vertical-align: 0.5;
+}
+```
+
+```text
+┌─────────────────────────────────────────────────────────────────────┐ 
+│ element                                                             │ 
+│ ┌─────────────────────────────────────────────┐ ┌─────────────────┐ │ 
+│ │                                             │ │    element      │ │ 
+│ │element-text                                 │ │       ─         │ │ 
+│ │                                             │ │     icon        │ │ 
+│ └─────────────────────────────────────────────┘ └─────────────────┘ │ 
+└─────────────────────────────────────────────────────────────────────┘ 
+```
+
+We can also specify the color and width of the cursor. You could, for example,
+create a crimson block cursor like this:
+
+```css
+entry {
+  cursor-color: rgb(220,20,60);
+  cursor-width: 8px;
+}
+```
+
+By default, the `cursor-color` will be the same as the `text-color`. The
+`cursor-width` will always default to 2 pixels.
+
+If you want to see the complete theme, including the modification you can run:
+
+```bash
+rofi -dump-theme
+```
+
+## Default theme loading
+
+By default, rofi loads the default theme. This theme is **always** loaded.
+The default configuration contains:
+
+```css
+@theme "default"
+```
+
+To unload the default theme, and load another theme, add the `@theme` statement
+to your `config.rasi` file.
+
+If you have a theme loaded via `@theme` or use the default theme, you can tweak
+it by adding overriding elements at the end of your `config.rasi` file.
+
+For the difference between `@import` and `@theme` see the `Multiple file
+handling` section in this manpage.
+
+To see the default theme, run the following command:
+
+```bash
+rofi -no-config -dump-theme
+```
+
+## Description
+
+The need for a new theme format was motivated by the fact that the way rofi
+handled widgets has changed. From a very static drawing of lines and text to a
+nice structured form of packing widgets. This change made it possible to
+provide a more flexible theme framework. The old theme format and config file
+are not flexible enough to expose these options in a user-friendly way.
+Therefore, a new file format has been created, replacing the old one.
+
+## Format specification
+
+## Encoding
+
+The encoding of the file is UTF-8. Both unix (`\n`) and windows (`\r\n`)
+newlines format are supported. But unix is preferred.
+
+## Comments
+
+C and C++ file comments are supported.
+
+-   Anything after  `// ` and before a newline is considered a comment.
+
+-   Everything between `/*` and `*/` is a comment, this comment can span
+    multiple lines.
+
+Comments can be nested and the C comments can be inline.
+
+The following is valid:
+
+```css
+// Magic comment.
+property: /* comment */ value;
+```
+
+However, this is not:
+
+```css
+prop/*comment*/erty: value;
+```
+
+## White space
+
+White space and newlines, like comments, are ignored by the parser.
+
+This:
+
+```css
+property: name;
+```
+
+Is identical to:
+
+```css
+     property             :
+name
+
+;
+```
+
+## File extension
+
+The preferred file extension for the new theme format is **rasi**. This is an
+abbreviation for **r**ofi **a**dvanced **s**tyle **i**nformation. If a theme
+file is split over multiple files, include files can have the: **rasinc**
+extension.
+
+## Basic Structure
+
+Each element has a section with defined properties. Global properties can be
+defined in section `* { }`. Sub-section names begin with an optional hash
+symbol `#`.
+
+It is advised to define the *global properties section* on top of the file to
+make inheritance of properties clearer.
+
+```css
+/* Global properties section */
+* {
+    // list of properties
+}
+
+/* Element theme section. */
+{element path} {
+    // list of properties
+}
+{elements... } {
+    // list of properties
+}
+```
+
+If there are multiple sections with the same name, they are merged. Duplicate
+properties are overwritten and the last parsed entry kept.
+
+## Global properties section
+
+A theme can have one or more global properties sections. If there is more than
+one, they will be merged.
+
+The global properties section denotes the defaults for each element.
+Each property of this section can be referenced with `@{identifier}`
+(See Properties section)
+
+A global properties section is indicated with a `*` as element path.
+
+## Element theme section
+
+A theme can have multiple element theme sections.
+
+The element path can consist of multiple names separated by whitespace or dots.
+Each element may contain any number of letters, numbers and `-`'s.
+The first element in the element path can optionally start with a `#` (for
+historic reasons). Multiple elements can be specified by a `,`.
+
+This is a valid element name:
+
+```css
+element normal.normal {
+    background-color: blue;
+}
+button {
+    background-color: blue;
+}
+```
+
+And is identical to:
+
+```css
+element normal normal, button {
+    background-color: blue;
+}
+```
+
+Each section inherits the global properties. Properties can be explicitly
+inherited from their parent with the `inherit` keyword.
+In the following example:
+
+```css
+window {
+ a: 1;
+ b: 2;
+ children: [ mainbox ];
+}
+mainbox {
+    a: inherit;
+    b: 4;
+    c: 8;
+}
+```
+
+The element `mainbox` will have the following set of properties (if `mainbox`
+is a child of `window`):
+
+```css
+a: 1;
+b: 4;
+c: 8;
+```
+
+If multiple sections are defined with the same name, they are merged by the
+parser. If multiple properties with the same name are defined in one section,
+the last encountered property is used.
+
+## Properties Format
+
+The properties in a section consist of:
+
+```css
+{identifier}: {value};
+```
+
+Both fields are mandatory for a property.
+
+The `identifier` names the specified property. Identifiers can consist of any
+combination of numbers, letters and '-'. It must not contain any whitespace.
+The structure of the `value` defines the type of the property. The current
+parser does not define or enforce a certain type of a particular `identifier`.
+When used, values with the wrong type that cannot be converted are ignored.
+
+The current theme format supports different types:
+
+- a string
+- an integer number
+- a fractional number
+- a boolean value
+- a color
+- image
+- text style
+- line style
+- a distance
+- a padding
+- a border
+- a position
+- a reference
+- an orientation
+- a cursor
+- a list of keywords
+- an array of values
+- an environment variable
+- Inherit
+
+Some of these types are a combination of other types.
+
+### String
+
+- Format:  `(["'])[:print:]+\1`
+
+Strings are always surrounded by double (`"`) or single (`'`, apostrophe) quotes. Between
+the quotes there can be any printable character.
+
+For example:
+
+```css
+font: "Awasome 12";
+```
+
+The string must be valid UTF-8, special characters can be escaped:
+
+```css
+text { content: "Line one\n\tIndented line two 'Quoted text'"; }
+text { content: 'Line one\n\tIndented line two "Quoted text"'; }
+text { content: "Line one\n\tIndented line two \"Quoted text\""; }
+```
+
+The following special characters can be escaped: `\b`, `\f`, `\n`, `\r`, `\t`, `\v`, `\`,
+`"` and `'` (double quotes inside single-quotes or in reverse don't need escape).
+
+### Integer
+
+- Format: `[-+]?[:digit:]+`
+
+An integer may contain any number.
+
+For examples:
+
+```css
+lines: 12;
+```
+
+### Real
+
+- Format: `[-+]?[:digit:]+(\.[:digit:]+)?`
+
+A real is an integer with an optional fraction.
+
+For example:
+
+```css
+real: 3.4;
+```
+
+The following is not valid: `.3`, `3.` or scientific notation: `3.4e-3`.
+
+### Boolean
+
+- Format: `(true|false)`
+
+Boolean value is either `true` or `false`. This is case-sensitive.
+
+For example:
+
+```css
+dynamic: false;
+```
+
+### Image
+
+**rofi** support a limited set of background-image formats.
+
+-   Format: url("path to image");
+
+-   Format: url("path to image", scale);
+    where scale is: none, both, width, height
+
+-   Format: linear-gradient(stop color,stop1, color, stop2 color, ...);
+
+-   Format: linear-gradient(to direction, stop color,stop1, color, stop2 color,
+    ...); where direction is:   top,left,right,bottom.
+
+-   Format: linear-gradient(angle, stop color,stop1, color, stop2 color, ...);
+    Angle in deg,rad,grad (as used in color).
+
+Where the `path` is a string, and `stop` color is of type color.
+
+### Color
+
+**rofi** supports the color formats as specified in the CSS standard (1,2,3 and
+some of CSS 4)
+
+-   Format: `#{HEX}{3}` (rgb)
+
+-   Format: `#{HEX}{4}` (rgba)
+
+-   Format: `#{HEX}{6}` (rrggbb)
+
+-   Format: `#{HEX}{8}` (rrggbbaa)
+
+-   Format: `rgb[a]({INTEGER},{INTEGER},{INTEGER}[, {PERCENTAGE}])`
+
+-   Format: `rgb[a]({INTEGER}%,{INTEGER}%,{INTEGER}%[, {PERCENTAGE}])`
+
+-   Format: `hsl[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
+
+-   Format: `hwb[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
+
+-   Format: `cmyk( {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE} [,
+    {PERCENTAGE} ])`
+
+-   Format: `{named-color} [ / {PERCENTAGE} ]`
+
+The white-space format proposed in CSS4 is also supported.
+
+The different values are:
+
+-   `{HEX}` is a hexadecimal number ('0-9a-f' case insensitive).
+
+-   `{INTEGER}` value can be between 0 and 255 or 0-100 when representing
+    percentage.
+
+-   `{ANGLE}` is the angle on the color wheel, can be in `deg`, `rad`, `grad`
+    or `turn`. When no unit is specified, degrees is assumed.
+
+-   `{PERCENTAGE}` can be between 0-1.0, or 0%-100%
+
+-   `{named-color}` is one of the following colors:
+
+    AliceBlue, AntiqueWhite, Aqua, Aquamarine, Azure, Beige, Bisque, Black,
+    BlanchedAlmond, Blue, BlueViolet, Brown, BurlyWood, CadetBlue, Chartreuse,
+    Chocolate, Coral, CornflowerBlue, Cornsilk, Crimson, Cyan, DarkBlue,
+    DarkCyan, DarkGoldenRod, DarkGray, DarkGrey, DarkGreen, DarkKhaki,
+    DarkMagenta, DarkOliveGreen, DarkOrange, DarkOrchid, DarkRed, DarkSalmon,
+    DarkSeaGreen, DarkSlateBlue, DarkSlateGray, DarkSlateGrey, DarkTurquoise,
+    DarkViolet, DeepPink, DeepSkyBlue, DimGray, DimGrey, DodgerBlue, FireBrick,
+    FloralWhite, ForestGreen, Fuchsia, Gainsboro, GhostWhite, Gold, GoldenRod,
+    Gray, Grey, Green, GreenYellow, HoneyDew, HotPink, IndianRed, Indigo,
+    Ivory, Khaki, Lavender, LavenderBlush, LawnGreen, LemonChiffon, LightBlue,
+    LightCoral, LightCyan, LightGoldenRodYellow, LightGray, LightGrey,
+    LightGreen, LightPink, LightSalmon, LightSeaGreen, LightSkyBlue,
+    LightSlateGray, LightSlateGrey, LightSteelBlue, LightYellow, Lime,
+    LimeGreen, Linen, Magenta, Maroon, MediumAquaMarine, MediumBlue,
+    MediumOrchid, MediumPurple, MediumSeaGreen, MediumSlateBlue,
+    MediumSpringGreen, MediumTurquoise, MediumVioletRed, MidnightBlue,
+    MintCream, MistyRose, Moccasin, NavajoWhite, Navy, OldLace, Olive,
+    OliveDrab, Orange, OrangeRed, Orchid, PaleGoldenRod, PaleGreen,
+    PaleTurquoise, PaleVioletRed, PapayaWhip, PeachPuff, Peru, Pink, Plum,
+    PowderBlue, Purple, RebeccaPurple, Red, RosyBrown, RoyalBlue, SaddleBrown,
+    Salmon, SandyBrown, SeaGreen, SeaShell, Sienna, Silver, SkyBlue, SlateBlue,
+    SlateGray, SlateGrey, Snow, SpringGreen, SteelBlue, Tan, Teal, Thistle,
+    Tomato, Turquoise, Violet, Wheat, White, WhiteSmoke, Yellow,
+    YellowGreen,transparent
+
+For example:
+
+```css
+background-color: #FF0000;
+border-color: rgba(0,0,1, 0.5);
+text-color: SeaGreen;
+```
+or
+
+```css
+background-color: transparent;
+text-color: Black;
+```
+
+### Text style
+
+- Format: `(bold|italic|underline|strikethrough|none)`
+
+Text style indicates how the highlighted text is emphasized. `None` indicates
+that no emphasis should be applied.
+
+- `bold`: make the text thicker then the surrounding text.
+- `italic`: put the highlighted text in script type (slanted).
+- `underline`: put a line under the text.
+- `strikethrough`: put a line through the text.
+
+The following options are available on pango 1.50.0 and up:
+
+- `uppercase`: Uppercase the text.
+- `lowercase`: Lowercase the text.
+
+The following option is disabled as pango crashes on this if there is eel
+upsizing or wrapping. This will be re-enabled once fixed:
+
+- `capitalize`: Capitalize the text.
+
+### Line style
+
+- Format: `(dash|solid)`
+
+Indicates how a line should be drawn.
+It currently supports:
+- `dash`:  a dashed line, where the gap is the same width as the dash
+- `solid`: a solid line
+
+### Distance
+
+- Format: `{Integer}px`
+- Format: `{Real}em`
+- Format: `{Real}ch`
+- Format: `{Real}%`
+- Format: `{Real}mm`
+
+A distance can be specified in 3 different units:
+
+- `px`: Screen pixels.
+- `em`: Relative to text height.
+- `ch`: Relative to width of a single number.
+- `mm`: Actual size in millimeters (based on dpi).
+- `%`:  Percentage of the **monitor** size.
+
+Distances used in the horizontal direction use the monitor width. Distances in
+the vertical direction use the monitor height.
+For example:
+
+```css
+   padding: 10%;
+```
+On a full-HD (1920x1080) monitor, it defines a padding of 192 pixels on the left
+and right side and 108 pixels on the top and bottom.
+
+#### Calculating sizes
+
+Rofi supports some maths in calculating sizes. For this it uses the CSS syntax:
+
+```css
+width: calc( 100% - 37px );
+```
+
+```css
+width: calc( 20% min 512 );
+```
+
+It supports the following operations:
+
+- `+`      : Add
+- `-`      : Subtract
+- `/`      : Divide
+- `-`      : Multiply
+- `modulo` : Modulo
+- `min`    : Minimum of lvalue or rvalue;
+- `max`    : Maximum of lvalue or rvalue;
+- `floor`  : Round down lvalue to the next multiple of rvalue 
+- `ceil`   : Round up lvalue to the next multiple of rvalue 
+- `round`  : Round lvalue to the next multiple of rvalue 
+
+It uses the C precedence ordering.
+
+### Padding
+
+- Format: `{Integer}`
+- Format: `{Distance}`
+- Format: `{Distance} {Distance}`
+- Format: `{Distance} {Distance} {Distance}`
+- Format: `{Distance} {Distance} {Distance} {Distance}`
+
+If no unit is specified, pixels are assumed.
+
+The different number of fields in the formats are parsed like:
+
+- 1 field: `all`
+- 2 fields: `top&bottom` `left&right`
+- 3 fields: `top`, `left&right`, `bottom`
+- 4 fields: `top`, `right`, `bottom`, `left`
+
+### Border
+
+-   Format: `{Integer}`
+
+-   Format: `{Distance}`
+
+-   Format: `{Distance} {Distance}`
+
+-   Format: `{Distance} {Distance} {Distance}`
+
+-   Format: `{Distance} {Distance} {Distance} {Distance}`
+
+-   Format: `{Distance} {Line style}`
+
+-   Format: `{Distance} {Line style} {Distance} {Line style}`
+
+-   Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
+    style}`
+
+-   Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
+    style} {Distance} {Line style}`
+
+Borders are identical to padding, except that each distance field has a line
+style property.
+
+> When no unit is specified, pixels are assumed.
+
+### Position
+
+Indicate a place on the window/monitor.
+
+```text
+┌─────────────┬─────────────┬─────────────┐
+│ north west  │    north    │  north east │
+├─────────────┼─────────────┼─────────────┤
+│   west      │   center    │     east    │
+├─────────────┼─────────────┼─────────────┤
+│ south west  │    south    │  south east │
+└─────────────┴─────────────┴─────────────┘
+```
+
+- Format: `(center|east|north|west|south|north east|north west|south west|south
+  east)`
+
+### Visibility
+
+It is possible to hide widgets:
+
+```css
+inputbar {
+    enabled: false;
+}
+```
+
+### Reference
+
+- Format: `@{PROPERTY NAME}`
+
+A reference can point to another reference. Currently, the maximum number of
+redirects is 20. A property always refers to another property. It cannot be
+used for a subpart of the property. For example, this is not valid:
+
+```css
+highlight: bold @pink;
+```
+
+But this is:
+
+```css
+* {
+    myhigh: bold #FAA;
+}
+
+window {
+    highlight: @myhigh;
+}
+```
+
+- Format: `var(PROPERTY NAME, DEFAULT)`
+
+A reference can point to another reference. Currently, the maximum number of
+redirects is 20. A property always refers to another property. It cannot be
+used for a subpart of the property.
+
+Example:
+
+```css
+window {
+    width: var( width, 30%);
+}
+```
+
+If the property `width` is set globally (`*{}`) that value is used, if the
+property `width` is not set, the default value is used.
+
+### Orientation
+
+- Format: `(horizontal|vertical)`
+
+Specify the orientation of the widget.
+
+### Cursor
+
+- Format: `(default|pointer|text)`
+
+Specify the type of mouse cursor that is set when the mouse pointer is over the
+widget.
+
+### List of keywords
+
+- Format: `[ keyword, keyword ]`
+
+A list starts with a '[' and ends with a ']'. The entries in the list are
+comma-separated. The `keyword` in the list refers to an widget name.
+
+### List of values
+
+- Format: `[ value, value, ... ]`
+
+An list starts with a '[' and ends with a ']'. The entries in the list are
+comma-separated.
+
+### Environment variable
+
+- Format: `${:alnum:}`
+
+This will parse the environment variable as the property value. (that then can
+be any of the above types). The environment variable should be an alphanumeric
+string without white-space.
+
+```css
+* {
+    background-color: ${BG};
+}
+```
+
+- Format: `env(ENVIRONMENT, default)`
+
+This will parse the environment variable as the property value. (that then can
+be any of the above types). The environment variable should be an alphanumeric
+string without white-space. If the environment value is not found, the default
+value is used.
+
+```css
+window {
+    width: env(WIDTH, 40%);
+}
+```
+
+If environment WIDTH is set, then that value is parsed, otherwise the default
+value (`40%`).
+
+### Inherit
+
+- Format: `inherit`
+
+Inherits the property from its parent widget.
+
+```css
+mainbox {
+    border-color: inherit;
+}
+```
+
+## Elements paths
+
+Element paths exists of two parts, the first part refers to the actual widget
+by name. Some widgets have an extra state.
+
+For example:
+
+```css
+element selected {
+}
+```
+
+Here `element selected` is the name of the widget, `selected` is the state of
+the widget.
+
+The difference between dots and spaces is purely cosmetic. These are all the
+same:
+
+```css
+element .selected {
+
+element.selected {
+}
+element selected {
+}
+```
+
+### Supported element paths
+
+### Base widgets
+
+The default widgets available in **rofi** and the default hierarchic:
+
+- `window`
+  -   `overlay`: the overlay widget.
+
+  -   `mainbox`: The mainbox box.
+
+   -   `inputbar`: The input bar box.
+       -   `box`: the horizontal @box packing the widgets
+
+          -   `case-indicator`: the case/sort indicator @textbox
+
+          -   `prompt`: the prompt @textbox
+
+          -   `entry`: the main entry @textbox
+
+          -   `num-rows`: Shows the total number of rows.
+
+          -   `num-filtered-rows`: Shows the total number of rows after
+              filtering.
+
+          -   `textbox-current-entry`: Shows the text of the currently selected
+              entry.
+
+          -   `icon-current-entry`: Shows the icon of the currently selected
+              entry.
+
+   -   `listview`: The listview.
+
+       -   `scrollbar`: the listview scrollbar
+
+       -   `element`: a box in the listview holding the entries
+
+	     -   `element-icon`: the widget in the listview's entry showing the
+		 (optional) icon
+
+	     -   `element-index`: the widget in the listview's entry
+		 keybindable index (1,2,3..0)
+
+	     -   `element-text`: the widget in the listview's entry showing the
+		 text.
+
+   -   `mode-switcher`: the main horizontal @box packing the buttons.
+       - `button`: the buttons @textbox for each mode
+
+   -   `message`: The container holding the textbox.
+       - `textbox`: the message textbox
+
+Note that these path names match the default theme. Themes that provide a
+custom layout will have different elements, and structure.
+
+### State
+
+State: State of widget
+
+Optional flag(s) indicating state of the widget, used for theming.
+
+These are appended after the name or class of the widget.
+
+#### Example
+
+```
+button selected.normal { }
+
+element selected.urgent { }
+```
+
+Currently only the entrybox and scrollbar have states:
+
+#### Entrybox
+
+```
+{visible modifier}.{state}
+```
+
+Where `visible modifier` can be:
+- normal: no modification
+- selected: the entry is selected/highlighted by user
+- alternate: the entry is at an alternating row (uneven row)
+
+Where `state` is:
+- normal: no modification
+- urgent: this entry is marked urgent
+- active: this entry is marked active
+
+These can be mixed.
+
+Example:
+
+```css
+nametotextbox selected.active {
+    background-color: #003642;
+    text-color: #008ed4;
+}
+```
+
+Sets all selected textboxes marked active to the given text and background
+color. Note that a state modifies the original element, it therefore contains
+all the properties of that element.
+
+#### Scrollbar
+
+The scrollbar uses the `handle` state when drawing the small scrollbar handle.
+This allows the colors used for drawing the handle to be set independently.
+
+## Widget properties
+
+The following properties are currently supported:
+
+###  all widgets
+
+-   **enabled**:           enable/disable rendering of the widget
+
+-   **padding**:           padding
+    Padding on the inside of the widget
+
+-   **margin**:            padding
+    Margin on the outside of the widget
+
+-   **border**:            border
+    Border around the widget (between padding and margin)/
+
+-   **border-radius**:     padding
+    Sets a radius on the corners of the borders.
+
+-   **background-color**:  color
+    Background color
+
+-   **background-image**:  image
+    Background image
+
+-   **border-color**:      color
+    Color of the border
+
+-   **cursor**:            cursor
+    Type of mouse cursor that is set when the mouse pointer is hovered over the
+    widget.
+
+### window
+
+-   **font**:            string
+    The font used in the window
+
+-   **transparency**:    string
+    Indicating if transparency should be used and what type:
+    - **real** - True transparency. Only works with a compositor.
+    - **background** - Take a screenshot of the background image and use that.
+    - **screenshot** - Take a screenshot of the screen and use that.
+    - **Path** to png file - Use an image.
+
+-   **location**:       position
+      The place of the anchor on the monitor
+
+-   **anchor**:         anchor
+      The anchor position on the window
+
+-   **fullscreen**:     boolean Window is fullscreen.
+
+-   **width**:          distance The width of the window
+
+-   **x-offset**:       distance
+
+-   **y-offset**:       distance The offset of the window to the anchor point,
+    allowing you to push the window left/right/up/down
+
+### scrollbar Properties
+
+- **background-color**:    color
+- **handle-width**:        distance
+- **handle-color**:        color
+- **border-color**:        color
+
+### box
+
+- **orientation**:      orientation Set the direction the elements are packed.
+- **spacing**:          distance Distance between the packed elements.
+
+### textbox
+
+-   **background-color**:  color
+
+-   **border-color**:      the color used for the border around the widget.
+
+-   **font**:              the font used by this textbox (string).
+
+-   **str**/**content**:   the string to display by this textbox (string).
+
+-   **vertical-align**:    Vertical alignment of the text. A number between 0
+    (top) and 1 (bottom).
+
+-   **horizontal-align**:  Horizontal alignment of the text. A number between 0
+    (left) and 1 (right).
+
+-   **text-color**:        the text color to use.
+
+-   **text-transform**:    text style {color} for the whole text.
+
+-   **highlight**:         text style {color}. color is optional, multiple
+    highlight styles can be added like: bold underline italic #000000; This
+    option is only available on the `element-text` widget.
+
+-   **width**:             override the desired width for the textbox.
+
+-   **content**:           Set the displayed text (String).
+
+-   **placeholder**:       Set the displayed text (String) when nothing is
+    entered.
+
+-   **placeholder-markup**:       If true, placeholder text supports pango
+    markup for stylizing.
+
+-   **placeholder-color**: Color of the placeholder text.
+
+-   **blink**:             Enable/Disable blinking on an input textbox
+    (Boolean).
+
+-   **markup**:            Force markup on, beware that only valid pango markup
+    strings are shown.
+
+-   **tab-stops**:         array of distances. Set the location of tab stops by
+    their distance from the beginning of the line. Each distance should be
+    greater than the previous one. The text appears to the right of the tab
+    stop position (other alignments are not supported yet).
+
+-   **cursor-width**:      The width of the cursor.
+
+-   **cursor-color**:      The color used to draw the cursor.
+
+-   **cursor-outline**:      Enable a border (outline) around the cursor.
+    (Boolean)
+
+-   **cursor-outline-width**: The width of the border around the cursor.
+    (Double)
+
+-   **cursor-outline-color**: The color to use for the cursor outline.
+    (Color)
+
+-   **text-outline**:      Enable a border (outline) around the text. (Boolean)
+
+-   **text-outline-width**: The width of the border around the text.  (Double)
+
+-   **text-outline-color**: The color to use for the text outline.    (Color)
+
+### listview
+-   **columns**:         integer Number of columns to show (at least 1)
+
+-   **fixed-height**:    boolean Always show `lines` rows, even if fewer
+    elements are available.
+
+-   **dynamic**:         boolean `True` if the size should change when filtering
+    the list, `False` if it should keep the original height.
+
+-   **scrollbar**:       boolean If the scrollbar should be enabled/disabled.
+
+-   **scrollbar-width**: distance Width of the scrollbar
+
+-   **cycle**:           boolean When navigating, it should wrap around
+
+-   **spacing**:         distance Spacing between the elements (both vertical
+    and horizontal)
+
+-   **lines**:           integer Number of rows to show in the list view.
+
+-   **layout**:           orientation Indicate how elements are stacked.
+    Horizontal implements the dmenu style.
+
+-   **reverse**:         boolean Reverse the ordering (top down to bottom up).
+
+-   **flow**:           orientation The order the elements are layed out.
+    Vertical is the original 'column' view.
+
+-   **fixed-columns**:    boolean Do not reduce the number of columns shown when
+    number of visible elements is not enough to fill them all.
+
+-   **require-input**:    boolean Listview requires user input to be unhidden.
+    The list is still present and hitting accept will activate the first entry.
+
+## Listview widget
+
+The listview widget is special container widget.
+It has the following fixed children widgets:
+
+-   0 or more `element` widgets of the type box.
+
+-   An optional `scrollbar` widget. This can be enabled using the scrollbar
+    property.
+
+These cannot be changed using the `children` property.
+
+Each Entry displayed by listview is captured by a `box` called `element`.
+An `element` widget can contain the following special child widgets:
+
+- `element-icon`: An icon widget showing the icon associated to the entry.
+- `element-text`: A textbox widget showing the text associated to the entry.
+- `element-index`: A textbox widget that shows the shortcut keybinding number.
+
+By default the `element-icon` and `element-text` child widgets are added to the
+`element`. This can be modified using the `children` property or the
+`[no]-show-icons` option.
+
+A child added with another name is treated the same as the special widget
+described in the [advanced layout](#advanced-layout) section.
+
+### listview text highlight
+
+The `element-text` widget in the `listview` is the one used to show the text.
+On this widget set the `highlight` property (only place this property is used)
+to change the style of highlighting. The `highlight` property consist of the
+`text-style` property and a color.
+
+To disable highlighting:
+
+```css
+  element-text {
+    highlight: None;
+  }
+```
+
+To set to red underlined:
+
+```css
+  element-text {
+    highlight: underline red;
+  }
+```
+
+## Layout
+
+The new format allows the layout of the **rofi** window to be tweaked
+extensively. For each widget, the themer can specify padding, margin, border,
+font, and more. It even allows, as an advanced feature, to pack widgets in a
+custom structure.
+
+### Basic layout structure
+
+The whole view is made out of boxes that pack other boxes or widgets.
+The box can be vertical or horizontal. This is loosely inspired by [GTK](http://gtk.org/).
+
+The current layout of **rofi** is structured as follows:
+
+```text
+┌────────────────────────────────────────────────────────────────────────────────────┐
+│ window {BOX:vertical}                                                              │
+│ ┌───────────────────────────────────────────────────────────────────────────────┐  │
+│ │ mainbox  {BOX:vertical}                                                       │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │ inputbar {BOX:horizontal}                                                 │ │  │
+│ │ │ ┌─────────┐ ┌─┐ ┌───────────────────────────────┐ ┌───┐ ┌───┐ ┌───┐ ┌───┐ │ │  │
+│ │ │ │ prompt  │ │:│ │ entry                         │ │#fr│ │ / │ │#ns│ │ci │ │ │  │
+│ │ │ └─────────┘ └─┘ └───────────────────────────────┘ └───┘ └───┘ └───┘ └───┘ │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ │                                                                               │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │ message                                                                   │ │  │
+│ │ │ ┌───────────────────────────────────────────────────────────────────────┐ │ │  │
+│ │ │ │ textbox                                                               │ │ │  │
+│ │ │ └───────────────────────────────────────────────────────────────────────┘ │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ │                                                                               │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │ listview                                                                  │ │  │
+│ │ │ ┌─────────────────────────────────────────────────────────────────────┐   │ │  │
+│ │ │ │ element                                                             │   │ │  │
+│ │ │ │ ┌─────────────────┐ ┌─────────────────────────────────────────────┐ │   │ │  │
+│ │ │ │ │element─icon     │ │element─text                                 │ │   │ │  │
+│ │ │ │ └─────────────────┘ └─────────────────────────────────────────────┘ │   │ │  │
+│ │ │ └─────────────────────────────────────────────────────────────────────┘   │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ │                                                                               │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │  mode─switcher {BOX:horizontal}                                           │ │  │
+│ │ │ ┌───────────────┐   ┌───────────────┐  ┌──────────────┐ ┌───────────────┐ │ │  │
+│ │ │ │ Button        │   │ Button        │  │ Button       │ │ Button        │ │ │  │
+│ │ │ └───────────────┘   └───────────────┘  └──────────────┘ └───────────────┘ │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ └───────────────────────────────────────────────────────────────────────────────┘  │
+└────────────────────────────────────────────────────────────────────────────────────┘
+
+
+```
+> - ci is the case-indicator
+> - fr is the num-filtered-rows
+> - ns is the num-rows
+
+### Error message structure
+
+```text
+┌──────────────────────────────────────────────────────────────────────────────────┐
+│ window {BOX:vertical}                                                            │
+│ ┌─────────────────────────────────────────────────────────────────────────────┐  │
+│ │ error─message {BOX:vertical}                                                │  │
+│ │ ┌────────────────────────────────────────────────────────────────────────┐  │  │
+│ │ │ textbox                                                                │  │  │
+│ │ └────────────────────────────────────────────────────────────────────────┘  │  │
+│ └─────────────────────────────────────────────────────────────────────────────┘  │
+└──────────────────────────────────────────────────────────────────────────────────┘
+
+```
+
+### Advanced layout
+
+The layout of **rofi** can be tweaked by packing the 'fixed' widgets in a
+custom structure.
+
+The following widgets are fixed, as they provide core **rofi** functionality:
+
+- prompt
+- entry
+- overlay
+- case-indicator
+- message
+- listview
+- mode-switcher
+- num-rows
+- num-filtered-rows
+
+The following keywords are defined and can be used to automatically pack a
+subset of the widgets. These are used in the default theme as depicted in the
+figure above.
+
+- mainbox Packs: `inputbar, message, listview, mode-switcher`
+- inputbar Packs: `prompt,entry,case-indicator`
+
+Any widget name starting with `textbox` is a textbox widget, others are box
+widgets and can pack other widgets.
+
+There are several special widgets that can be used by prefixing the name of the
+widget:
+
+#### Textbox widget
+
+This is a read-only textbox widget. The displayed string can be set with `content`.
+
+Example:
+
+```css
+textbox-custom {
+  expand: false;
+  content: "My Message";
+}
+```
+
+#### Icon
+
+This is an icon widget. The displayed icon can be set with `filename` and size
+with `size`. If the property `action` is set, it acts as a button. `action` can
+be set to a keybinding name and completes that action. (see rofi -show keys for
+a list).
+
+If the `squared` property is set to **false** the widget height and width are
+not forced to be equal.
+
+Example:
+
+```css
+icon-paste {
+    expand: false;
+    filename: "gtk-paste";
+    size: 24;
+    vertical-align: 0.5;
+    action: "kb-primary-paste";
+}
+```
+
+#### button
+
+This is a textbox widget that can have a 'clickable' action. The `action` can
+be set to: `keybinding`: accepts a keybinding name and completes that action.
+(see rofi -show keys for a list).
+
+```css
+button-paste {
+    expand: false;
+    content: "My Clickable Message";
+    vertical-align: 0.5;
+    action: "kb-primary-paste";
+}
+```
+
+#### Children
+
+To specify children, set the `children`
+property (this always happens on the `box` child, see example below):
+
+```css
+inputbar {
+  children: [prompt,entry,overlay,case-indicator];
+}
+```
+
+The theme needs to be updated to match the hierarchy specified.
+
+Below is an example of a theme emulating dmenu:
+
+```css
+* {
+    background-color:      Black;
+    text-color:            White;
+    border-color:          White;
+    font:            "Times New Roman 12";
+}
+
+window {
+    anchor:     north;
+    location:   north;
+    width:      100%;
+    padding:    4px;
+    children:   [ horibox ];
+}
+
+horibox {
+    orientation: horizontal;
+    children:   [ prompt, entry, listview ];
+}
+
+listview {
+    layout:     horizontal;
+    spacing:    5px;
+    lines:      10;
+}
+
+entry {
+    expand:     false;
+    width:      10em;
+}
+
+element {
+    padding: 0px 2px;
+}
+element selected {
+    background-color: SteelBlue;
+}
+```
+
+### Padding and margin
+
+Just like CSS, **rofi** uses the box model for each widget.
+
+```text
+┌──────────────────────────────────────────────────────────────────┐
+│ margin                                                           │
+│  ┌────────────────────────────────────────────────────────────┐  │
+│  │ border                                                     │  │
+│  │ ┌────────────────────────────────────────────────────────┐ │  │
+│  │ │ padding                                                │ │  │
+│  │ │ ┌────────────────────────────────────────────────────┐ │ │  │
+│  │ │ │ content                                            │ │ │  │
+│  │ │ └────────────────────────────────────────────────────┘ │ │  │
+│  │ └────────────────────────────────────────────────────────┘ │  │
+│  └────────────────────────────────────────────────────────────┘  │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Explanation of the different parts:
+
+-   Content - The content of the widget.
+
+-   Padding - Clears an area around the widget. The padding shows the
+    background color of the widget.
+
+-   Border - A border that goes around the padding and content. The border use
+    the border-color of the widget.
+
+-   Margin - Clears an area outside the border. The margin is transparent.
+
+The box model allows us to add a border around elements, and to define space
+between elements.
+
+The size of each margin, border, and padding can be set.
+For the border, a linestyle and radius can be set.
+
+### Spacing
+
+Widgets that can pack more then one child widget (currently box and listview)
+have the `spacing` property. This property sets the distance between the packed
+widgets (both horizontally and vertically).
+
+```text
+┌───────────────────────────────────────┐
+│ ┌────────┐ s ┌────────┐ s ┌────────┐  │
+│ │ child  │ p │ child  │ p │ child  │  │
+│ │        │ a │        │ a │        │  │
+│ │        │ c │        │ c │        │  │
+│ │        │ i │        │ i │        │  │
+│ │        │ n │        │ n │        │  │
+│ └────────┘ g └────────┘ g └────────┘  │
+└───────────────────────────────────────┘
+```
+
+### Advanced box packing
+
+More dynamic spacing can be achieved by adding dummy widgets, for example to
+make one widget centered:
+
+```text
+┌────────────────────────────────────────────────────┐
+│  ┌───────────────┐  ┌────────┐  ┌───────────────┐  │
+│  │ dummy         │  │ child  │  │ dummy         │  │
+│  │ expand: true; │  │        │  │ expand: true; │  │
+│  │               │  │        │  │               │  │
+│  │               │  │        │  │               │  │
+│  │               │  │        │  │               │  │
+│  └───────────────┘  └────────┘  └───────────────┘  │
+└────────────────────────────────────────────────────┘
+```
+
+If both dummy widgets are set to expand, `child` will be centered. Depending on
+the `expand` flag of child the remaining space will be equally divided between
+both dummy and child widget (expand enabled), or both dummy widgets (expand
+disabled).
+
+## Debugging
+
+To get debug information from the parser, run rofi like:
+
+```bash
+G_MESSAGES_DEBUG=Parser rofi -show run
+```
+
+Syntax errors are shown in a popup and printed out to command line with the
+above command.
+
+To see the elements queried during running, run:
+
+```bash
+G_MESSAGES_DEBUG=Theme rofi -show run
+```
+
+To test minor changes, part of the theme can be passed on the command line, for
+example to set it to full-screen:
+
+```bash
+rofi -theme-str 'window { fullscreen:true;}' -show run
+```
+
+Another syntax to modify theme properties is:
+
+```bash
+rofi -theme+window+fullscreen true -show run
+```
+
+To print the current theme, run:
+
+```bash
+rofi -dump-theme
+```
+
+## Media support
+
+Parts of the theme can be conditionally loaded, like the CSS `@media` option.
+
+```css
+@media ( min-width: 120 ) {
+
+}
+```
+
+It supports the following keys as constraint:
+
+- `min-width`:         load when width is bigger or equal then value.
+- `max-width`:         load when width is smaller then value.
+- `min-height`:        load when height is bigger or equal then value.
+- `max-height`:        load when height is smaller then value.
+- `min-aspect-ratio`   load when aspect ratio is over value.
+- `max-aspect-ratio`:  load when aspect ratio is under value.
+- `monitor-id`:        The monitor id, see rofi -help for id's.
+- `enabled`:           Boolean option to enable. Supports environment variable
+  or DMENU to detect if in dmenu mode.
+
+@media takes an integer number or a fraction, for integer number `px` can be
+added.
+
+```css
+@media ( min-width: 120 px ) {
+
+}
+```
+
+```css
+@media ( enabled: env(DO_LIGHT, false )) {
+
+}
+```
+
+```css
+@media ( enabled: DMENU) {
+
+}
+```
+
+## Conflicting constraints
+
+It is possible to define conflicting constraints in the theme. These conflicts
+are not explicitly reported. The most common example is forcing a specific
+window size, for example by enabling full-screen mode, having number of lines
+set in the listview and having the listview expand to available space. There is
+clearly a conflict in these 3 constraints. In this case, listview will not
+limit to the number of lines, but tries to fill the available space. It is up
+to the theme designer to make sure the theme handles this correctly.
+
+## Font Parsing
+
+Rofi uses [pango](https://pango.gnome.org/) for font rendering. The font should
+be specified in a format that pango understands. This normally is the font name
+followed by the font size. For example:
+
+```text
+mono 18
+```
+
+Or
+
+```text
+FontAwesome 22
+```
+
+From the pango manpage:
+
+The string must have the form
+
+```text
+\[FAMILY-LIST] \[STYLE-OPTIONS] \[SIZE] \[VARIATIONS]
+```
+
+where FAMILY-LIST is a comma-separated list of families optionally terminated
+by a comma, STYLE\_OPTIONS is a whitespace-separated list of words where each
+word describes one of style, variant, weight, stretch, or gravity, and SIZE is
+a decimal number (size in points) or optionally followed by the unit modifier
+“px” for absolute size. VARIATIONS is a comma-separated list of font variation
+specifications of the form “`axis`=value” (the = sign is optional).
+
+The following words are understood as styles: "Normal”, “Roman”, “Oblique”,
+“Italic”.
+
+The following words are understood as variants: “Small-Caps”, “All-Small-Caps”,
+“Petite-Caps”, “All-Petite-Caps”, “Unicase”, “Title-Caps”.
+
+The following words are understood as weights: “Thin”, “Ultra-Light”,
+“Extra-Light”, “Light”, “Semi-Light”, “Demi-Light”, “Book”, “Regular”,
+“Medium”, “Semi-Bold”, “Demi-Bold”, “Bold”, “Ultra-Bold”, “Extra-Bold”,
+“Heavy”, “Black”, “Ultra-Black”, “Extra-Black”.
+
+The following words are understood as stretch values: “Ultra-Condensed”,
+“Extra-Condensed”, “Condensed”, “Semi-Condensed”, “Semi-Expanded”, “Expanded”,
+“Extra-Expanded”, “Ultra-Expanded”.
+
+The following words are understood as gravity values: “Not-Rotated”, “South”,
+“Upside-Down”, “North”, “Rotated-Left”, “East”, “Rotated-Right”, “West”.
+
+Any one of the options may be absent. If FAMILY-LIST is absent, then the
+family\_name field of the resulting font description will be initialized to
+NULL. If STYLE-OPTIONS is missing, then all style options will be set to the
+default values. If SIZE is missing, the size in the resulting font description
+will be set to 0.
+
+A typical example:
+
+"Cantarell Italic Light 15 \`wght`=200"
+
+## Icon Handling 
+
+Rofi supports 3 ways of specifying an icon:
+
+- Filename
+- icon-name, this is looked up via the icon-theme.
+- Markup String. It renders a string as an icon.
+
+For the first two options, GdkPixbuf is used to open and render the icons.
+This in general gives support for most required image formats.
+For the string option it uses Pango to render the string. The string needs to
+start with a `<span` tag, that allows you to set color and font.
+
+Markup string:
+
+```bash
+echo -en "testing\0icon\x1f<span color='red'>⏻</span>" | ./rofi -dmenu
+```
+
+Getting supported icon formats:
+
+```bash
+G_MESSAGES_DEBUG=Helpers.IconFetcher rofi
+```
+This uses the debug framework and prints out a list of supported image  file
+extensions.
+
+## Multiple file handling
+
+The rasi file format offers two methods of including other files. This can be
+used to modify existing themes, or have multiple variations on a theme.
+
+- import:  Import and parse a second file.
+- theme:   Discard theme, and load file as a fresh theme.
+
+Syntax:
+
+```css
+@import "myfile"
+@theme "mytheme"
+```
+
+The specified file can either by *name*, *filename*,*full path*.
+
+If a filename is provided, it will try to resolve it in the following order:
+
+- If path is absolute and file exists, it will open the file. This includes expansion of '~' or '~user'
+- On an `@import` or `@theme` it looks in the directory of the file that tried to include it.
+- `${XDG_CONFIG_HOME}/rofi/themes/`
+- `${XDG_CONFIG_HOME}/rofi/`
+- `${XDG_DATA_HOME}/rofi/themes/`
+- `${INSTALL PREFIX}/share/rofi/themes/`
+
+A name is resolved (if it has no valid extension) as a filename by appending the `.rasi` extension.
+
+## Examples
+
+Several examples are installed together with **rofi**. These can be found in
+`{datadir}/rofi/themes/`, where `{datadir}` is the install path of **rofi**
+data. When installed using a package manager, this is usually: `/usr/share/`.
+
+## SEE ALSO
+
+rofi(1), rofi-script(5), rofi-theme-selector(1)
diff --git a/mkdocs/docs/1.7.6/rofi-thumbnails.5.markdown b/mkdocs/docs/1.7.6/rofi-thumbnails.5.markdown
new file mode 100644
index 000000000..e18ced7e1
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi-thumbnails.5.markdown
@@ -0,0 +1,85 @@
+# rofi-thumbnails(5)
+
+## NAME
+
+**rofi-thumbnails** - Rofi thumbnails system
+
+## DESCRIPTION
+
+**rofi** is now able to show thumbnails for all file types where an XDG compatible thumbnailer is present in the system.
+
+This is done by default in filebrowser and recursivebrowser mode, if **rofi** is launched with the `-show-icons` argument.
+
+In a custom user script or dmenu mode, it is possible to produce entry icons using XDG thumbnailers by adding the prefix `thumbnail://` to the filename
+specified after `\0icon\x1f`, for example:
+
+```bash
+echo -en "EntryName\0icon\x1fthumbnail://path/to/file\n" | rofi -dmenu -show-icons
+```
+
+### XDG thumbnailers
+
+XDG thumbnailers are files with a ".thumbnailer" suffix and a structure similar to ".desktop" files for launching applications. They are placed in `/usr/share/thumbnailers/` or `$HOME/.local/share/thumbnailers/`, and contain a list of mimetypes, for which is possible to produce the thumbnail image, and a string with the command to create said image. The example below shows the content of `librsvg.thumbnailer`, a thumbnailer for svg files using librsvg:
+
+```
+[Thumbnailer Entry]
+TryExec=/usr/bin/gdk-pixbuf-thumbnailer
+Exec=/usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
+MimeType=image/svg+xml;image/svg+xml-compressed;
+```
+
+The images produced are named as the md5sum of the input files and placed, depending on their size, in the XDG thumbnails directories: `$HOME/.cache/thumbnails/{normal,large,x-large,xx-large}`. They are then loaded by **rofi** as entry icons and can also be used by file managers like Thunar, Caja or KDE Dolphin to show their thumbnails. Additionally, if a thumbnail for a file is found in the thumbnails directories (produced previously by **rofi** or a file manager), **rofi** will load it instead of calling the thumbnailer.
+
+If a suitable thumbnailer for a given file is not found, **rofi** will try to use the corresponding mimetype icon from the icon theme. 
+
+### Custom command to create thumbnails
+
+It is possible to use a custom command to generate thumbnails for generic entry names, for example a script that downloads an icon given its url or selects different icons depending on the input. This can be done providing the `-preview-cmd` argument followed by a string with the command to execute, with the following syntax:
+
+```
+rofi ... -preview-cmd 'path/to/script_or_cmd "{input}" "{output}" "{size}"'
+```
+
+**rofi** will call the script or command substituting `{input}` with the input entry icon name (the string after `\0icon\x1fthumbnail://`), `{output}` with the output filename of the thumbnail and `{size}` with the requested thumbnail size. The script or command is responsible of producing a thumbnail image (if possible respecting the requested size) and saving it in the given `{output}` filename.
+
+### Issues with AppArmor
+
+In Linux distributions using AppArmor (such as Ubuntu and Debian), the default rules shipped can cause issues with thumbnails generation. If that is the case, AppArmor can be disabled by issuing the following commands
+
+```
+sudo systemctl stop apparmor
+sudo systemctl disable apparmor
+```
+
+In alternative, the following apparmor profile con be placed in a file named /etc/apparmor.d/usr.bin.rofi
+
+```
+#vim:syntax=apparmor
+# AppArmor policy for rofi
+
+#include <tunables/global>
+
+/usr/bin/rofi {
+    #include <abstractions/base>
+
+    # TCP/UDP network access for NFS
+    network inet  stream,
+    network inet6 stream,
+    network inet  dgram,
+    network inet6 dgram,
+
+    /usr/bin/rofi mr,
+
+    @{HOME}/ r,
+    @{HOME}/** rw,
+    owner @{HOME}/.cache/thumbnails/** rw,
+}
+```
+
+then run
+
+```
+apparmor_parser  -r /etc/apparmor.d/usr.bin.rofi
+```
+
+to reload the rule. This assumes that **rofi** binary is in /usr/bin, that is the case of a standard package installation.
diff --git a/mkdocs/docs/1.7.6/rofi.1.markdown b/mkdocs/docs/1.7.6/rofi.1.markdown
new file mode 100644
index 000000000..1193646c9
--- /dev/null
+++ b/mkdocs/docs/1.7.6/rofi.1.markdown
@@ -0,0 +1,1183 @@
+# rofi(1)
+
+## NAME
+
+**rofi** - A window switcher, application launcher, ssh dialog, dmenu
+replacement and more
+
+## SYNOPSIS
+
+**rofi** [ -show *mode* ]|[ -dmenu ]|[ -e *msg* ] [ CONFIGURATION ]
+
+## DESCRIPTION
+
+**rofi** is an X11 pop-up window switcher, run dialog, dmenu replacement, and
+more. It focuses on being fast to use and have minimal distraction. It supports
+keyboard and mouse navigation, type to filter, tokenized search and more.
+
+## USAGE
+
+**rofi**'s main functionality is to assist in your workflow, allowing you to
+quickly switch between windows, start applications or log into a remote machine
+via `ssh`. There are different *modes* for different types of actions. **rofi**
+is a standalone application and should not be integrated into scripts. For
+integration into scripts it has a special mode that functions as a (drop-in)
+replacement for **dmenu(1)**. See emulating dmenu below.
+
+### Running rofi
+
+To launch **rofi** directly in a certain mode, specify a mode with `rofi -show
+<mode>`. To show the `drun` dialog:
+
+```bash
+    rofi -show drun
+```
+
+A useful setup in minimalistic window managers is to combine `drun`, `run`
+with `window` mode:
+
+```bash
+  rofi -show combi -modes combi -combi-modes "window,drun,run"
+```
+
+In this setup it first list all open applications, then all installed
+applications. So if you type firefox and hit return, it will switch to the
+running firefox, or launch it when it is not running.
+
+### Emulating dmenu
+
+**rofi** can emulate **dmenu(1)** (a dynamic menu for X11) when launched with
+the `-dmenu` flag.
+
+For more information see **rofi-dmenu(5)**.
+
+### Display Error message
+
+**rofi** error dialog can also be called from the command line.
+
+```bash
+    rofi -e "my message"
+```
+
+Markup support can be enabled, see CONFIGURATION options.
+
+## CONFIGURATION
+
+There are currently three methods of setting configuration options (evaluated
+in order below):
+
+-   System configuration file  (for example `/etc/rofi.rasi`). It first checks
+    `XDG_CONFIG_DIRS`, and then `SYSCONFDIR` (that is passed at compile time).
+    It loads the first config file it finds, it does not merge multiple system
+    configuration files.
+
+-   Rasi theme file: The new *theme* format can be used to set configuration
+    values.
+
+-   Command-line options: Arguments passed to **rofi**.
+
+To get a template config file, run: `rofi -dump-config > config.rasi`
+
+This will contain (commented) all current configuration options, modified
+options are uncommented.
+
+To get a template config file that sets the icon-theme run: `rofi -icon-theme
+hicolor -dump-config`.
+
+It is **strongly** recommended to use this as a starting point for your
+configuration.
+
+An empty configuration section in the config file looks like:
+
+```css
+configuration {
+ // set config options here
+}
+```
+
+Most of the configuration options mentioned below (beside options like `-show`,
+`-dump-config` that apply to a single run) can be set here.
+
+For example to set the dpi value to 72:
+
+```css
+configuration {
+	dpi: 72;
+}
+```
+
+The configuration system supports the following types:
+
+- string
+- integer (signed and unsigned)
+- char
+- boolean
+- lists
+
+For the syntax of these options, see the **rofi-theme(5)** manpage.
+
+For use on the command line, Boolean options have a non-default command-line
+syntax. Example to enable option X:
+
+```text
+    -X
+```
+
+To disable option X:
+
+```text
+    -no-X
+```
+
+Below is a list of the most important options:
+
+### General
+
+`-help`
+
+The help option shows the full list of command-line options and the current set
+values. These include dynamic (run-time generated) options.
+
+`-version`
+
+Show the **rofi** version and exit.
+
+`-dump-config`
+
+Dump the current active configuration, in rasi format, to stdout and exit.
+Information about the rasi format can be found in the **rofi-theme(5)** manpage.
+
+`-dump-theme`
+
+Dump the current active theme, in rasi format, to stdout and exit.
+
+`-rasi-validate` *filename*
+
+Try to parse the file and return 0 when successful, non-zero when failed.
+
+`-list-keybindings`
+
+List all known keybindings without trying to parse them. This can be used to
+look for duplicate bindings.
+
+`-threads` *num*
+
+Specify the number of threads **rofi** should use:
+
+- 0: Autodetect the number of supported hardware threads.
+- 1: Disable threading
+- 2..n: Specify the maximum number of threads to use in the thread pool.
+
+Default:  Autodetect
+
+`-display` *display*
+
+The X server to contact. Default is `$DISPLAY`.
+
+`-dmenu`
+
+Run **rofi** in dmenu mode. This allows for interactive scripts.
+In `dmenu` mode, **rofi** reads from STDIN, and output to STDOUT.
+A simple example, displaying three pre-defined options:
+
+```bash
+    echo -e "Option #1\nOption #2\nOption #3" | rofi -dmenu
+```
+
+Or get the options from a script:
+
+```bash
+    ~/my_script.sh | rofi -dmenu
+```
+
+See the **rofi-dmenu(5)** manpage for more information.
+
+`-show` *mode*
+
+Open **rofi** in a certain mode. Available modes are `window`, `run`, `drun`,
+`ssh`, `combi`. The special argument `keys` can be used to open a searchable
+list of supported key bindings
+(see the **rofi-keys(5)** manpage)
+
+To show the run-dialog:
+
+```bash
+    rofi -show run
+```
+
+If `-show` is the last option passed to rofi, the first enabled modes is shown.
+
+`-modes` *mode1,mode2*
+
+Specify an ordered, comma-separated list of modes to enable.
+Enabled modes can be changed at runtime. Default key is `Ctrl+Tab`.
+If no modes are specified, all configured modes will be enabled.
+To only show the `run` and `ssh` launcher:
+
+```bash
+    rofi -modes "run,ssh" -show run
+```
+
+Custom modes can be added using the internal `script` mode. Each such mode has
+two parameters:
+
+```text
+<name>:<script>
+```
+
+Example: Have a mode called 'Workspaces' using the `i3_switch_workspaces.sh`
+script:
+
+```bash
+    rofi -modes "window,run,ssh,Workspaces:i3_switch_workspaces.sh" -show Workspaces
+```
+
+Notes: The i3 window manager dislikes commas in the command when specifying an
+exec command. For that case, `#` can be used as a separator.
+
+**TIP**: The name is allowed to contain spaces:
+
+```bash
+    rofi -modes "My File Browser:fb.sh" -show "My File Browser"
+```
+
+`-case-sensitive`
+
+Start in case-sensitive mode. This option can be changed at run-time using the
+`-kb-toggle-case-sensitivity` key binding.
+
+`-cycle`
+
+Cycle through the result list. Default is 'true'.
+
+`-filter` *filter*
+
+Filter the list by setting text in input bar to *filter*
+
+`-config` *filename*
+
+Load an alternative configuration file.
+
+`-cache-dir` *filename*
+
+Directory that is used to place temporary files, like history.
+
+`-scroll-method` *method*
+
+Select the scrolling method. 0: Per page, 1: continuous.
+
+`-normalize-match`
+
+Normalize the string before matching, so `o` will match `ö`, and `é` matches
+`e`.  This is not a perfect implementation, but works. For now, it disables
+highlighting of the matched part.
+
+`-no-lazy-grab`
+
+Disables lazy grab, this forces the keyboard being grabbed before gui is shown.
+
+`-no-plugins`
+
+Disable plugin loading.
+
+`-plugin-path` *directory*
+
+Specify the directory where **rofi** should look for plugins.
+
+`-show-icons`
+
+Show application icons in `drun` and `window` modes.
+
+`-icon-theme`
+
+Specify icon theme to be used. If not specified default theme from DE is used,
+*Adwaita* and *gnome* themes act as fallback themes.
+
+`-markup`
+
+Use Pango markup to format output wherever possible.
+
+`-normal-window`
+
+Make **rofi** react like a normal application window. Useful for scripts like
+Clerk that are basically an application.
+
+`-transient-window`
+
+Make **rofi** react like a modal dialog that is transient to the currently
+focused window. Useful when you use a keyboard shortcut to run and show
+on the window you are working with.
+
+`-[no-]steal-focus`
+
+Make rofi steal focus on launch and restore close to window that held it when
+launched.
+
+`-refilter-timeout-limit`
+
+The time (in ms) boundary filter may take before switch from instant to delayed
+filter mode.
+
+Default: 300
+
+A fallback icon can be specified for each mode:
+
+```css
+configuration {
+    <mode>{
+      fallback-icon: "<icon name>";
+    }
+}
+```
+Example
+
+```css
+configuration {
+    run,drun {
+      fallback-icon: "application-x-addon";
+    }
+}
+```
+
+### Matching
+
+`-matching` *method*
+
+Specify the matching algorithm used.
+Currently, the following methods are supported:
+
+- **normal**: match the int string
+- **regex**: match a regex input
+- **glob**: match a glob pattern
+- **fuzzy**: do a fuzzy match
+- **prefix**: match prefix
+
+Default: *normal*
+
+Note: glob matching might be slow for larger lists
+
+`-tokenize`
+
+Tokenize the input.
+
+`-drun-categories` *category1*,*category2*
+
+Only show desktop files that are present in the listed categories.
+
+`-drun-match-fields` *field1*,*field2*,...
+
+When using `drun`, match only with the specified Desktop entry fields.
+The different fields are:
+
+- **name**: the application's name
+- **generic**: the application's generic name
+- **exec**: the application's  executable
+- **categories**: the application's categories
+- **comment**: the application comment
+- **all**: all the above
+
+Default: *name,generic,exec,categories,keywords*
+
+`-drun-display-format`
+
+The format string for the `drun` dialog:
+
+- **name**: the application's name
+- **generic**: the application's generic name
+- **exec**: the application's  executable
+- **categories**: the application's categories
+- **comment**: the application comment
+- **url**: The url in case of a link type desktop file
+
+Pango markup can be used to formatting the output.
+
+Default: `{name} [<span weight='light' size='small'><i>({generic})</i></span>]`
+
+Note: Only fields enabled in `-drun-match-fields` can be used in the format
+string.
+
+`-[no-]drun-show-actions`
+
+Show actions present in the Desktop files.
+
+Default: false
+
+`-window-match-fields` *field1*,*field2*,...
+
+When using window mode, match only with the specified fields.
+The different fields are:
+
+- **title**: window's title
+- **class**: window's class
+- **role**: window's role
+- **name**: window's name
+- **desktop**: window's current desktop
+- **all**: all the above
+
+Default: *all*
+
+`-matching-negate-char` *char*
+
+Set the character used to negate the query (i.e. if it does **not** match the
+next keyword). Set to '\x0' to disable.
+
+Default: '-'
+
+### Filtered menu sort
+
+`-[no]-sort`
+
+Enable, disable sort for filtered menu.
+This setting can be changed at runtime (see `-kb-toggle-sort`).
+
+`-sorting-method` 'method' to specify the sort method.
+
+There are 2 methods:
+
+- **levenshtein** (Default)
+- **fzf**
+
+### Layout and Theming
+
+**IMPORTANT:** In newer **rofi** releases, all the theming options have been
+moved into the new theme format. They are no longer normal **rofi** options
+that can be passed directly on the command line (there are too many). Small
+snippets can be passed on the command line: `rofi -theme-str 'window {width:
+50%;}'` to override a single setting. They are merged into the current theme.
+They can also be appended at the end of the **rofi** config file to override
+parts of the theme.
+
+Most of the following options are **deprecated** and should not be used. Please
+use the new theme format to customize **rofi**. More information about the new
+format can be found in the **rofi-theme(5)** manpage.
+
+`-location`
+
+Specify where the window should be located. The numbers map to the following
+locations on screen:
+
+```text
+      1 2 3
+      8 0 4
+      7 6 5
+```
+
+Default: *0*
+
+`-fixed-num-lines`
+
+Keep a fixed number of visible lines. 
+
+`-sidebar-mode`
+
+Open in sidebar-mode. In this mode, a list of all enabled modes is shown at the
+bottom (See `-modes` option). To show sidebar, use:
+
+```bash
+    rofi -show run -sidebar-mode 
+```
+
+`-hover-select`
+
+Automatically select the entry the mouse is hovering over. This option is best
+combined with custom mouse bindings. To utilize hover-select and accept an
+entry in a single click, use:
+
+```bash
+    rofi -show run -hover-select -me-select-entry '' -me-accept-entry MousePrimary
+```
+
+`-eh` *number*
+
+Set row height (in chars)
+Default: *1*
+
+`-auto-select`
+
+When one entry is left, automatically select it.
+
+`-m` *num*,  `-m` *name*, `-monitor` *num*, `-monitor` *name*
+
+Select monitor to display **rofi** on. It accepts as input: *primary* (if
+primary output is set), the *xrandr* output name, or integer number (in order
+of detection). Negative numbers are handled differently:
+
+-   **-1**: the currently focused monitor.
+
+-   **-2**: the currently focused window (that is, **rofi** will be displayed
+    on top of the focused window).
+
+-   **-3**: Position of mouse (overrides the location setting to get normal
+    context menu behavior.)
+
+-   **-4**: the monitor with the focused window.
+
+-   **-5**: the monitor that shows the mouse pointer.
+
+Default: *-5*
+
+See `rofi -h` output for the detected monitors, their position, and size.
+
+`-theme` *filename*
+
+Path to the new theme file format. This overrides the old theme settings.
+
+`-theme-str` *string*
+
+Allow theme parts to be specified on the command line as an override.
+
+For example:
+
+```bash
+    rofi -theme-str '#window { fullscreen: true; }'
+```
+
+This option can be specified multiple times.
+This is now the method to tweak the theme via the command line.
+
+`-dpi`  *number*
+
+Override the default DPI setting.
+
+-   If set to `0`, it tries to auto-detect based on X11 screen size (similar to
+    i3 and GTK).
+
+-   If set to `1`, it tries to auto-detect based on the size of the monitor
+    that **rofi** is displayed on (similar to latest Qt 5).
+
+`-selected-row` *selected row*
+
+Select a certain row.
+
+Default: *0*
+
+### PATTERN setting
+
+`-terminal`
+
+Specify which terminal to start.
+
+```bash
+    rofi -terminal xterm
+```
+
+Pattern: *{terminal}*
+
+Default: *x-terminal-emulator*
+
+`-ssh-client` *client*
+
+Override the used `ssh` client.
+
+Pattern: *{ssh-client}*
+
+Default: *ssh*
+
+### SSH settings
+
+`-ssh-command` *cmd*
+
+Set the command to execute when starting an ssh session.
+The pattern *{host}* is replaced by the selected ssh entry.
+
+Pattern: *{ssh-client}*
+
+Default: *{terminal} -e {ssh-client} {host}*
+
+`-parse-hosts`
+
+Parse the `/etc/hosts` file for entries.
+
+Default: *disabled*
+
+`-[no-]parse-known-hosts`
+
+Parse the `~/.ssh/known_hosts` file for entries.
+
+Default: *enabled*
+
+### Run settings
+
+`-run-command` *cmd*
+
+Set command (*{cmd}*) to execute when running an application.
+See *PATTERN*.
+
+Default: *{cmd}*
+
+Example to run applications in a dedicated cgroup with systemd. Requires a
+shell to escape and interpolate the unit name correctly.
+
+```bash
+"bash -c 'systemd-run --user --unit=app-rofi-\$(systemd-escape {cmd})-\$RANDOM {cmd}'"
+```
+
+`-run-shell-command` *cmd*
+
+Set command to execute when running an application in a shell.
+See *PATTERN*.
+
+Default: *{terminal} -e {cmd}*
+
+`-run-list-command` *cmd*
+
+If set, use an external tool to generate a list of executable commands. Uses
+`run-command`.
+
+Default: *{cmd}*
+
+### Window switcher settings
+
+`-window-format` *format*
+
+Format what is being displayed for windows.
+
+*format*: {field[:len]}
+
+*field*:
+
+- **w**: desktop name
+- **t**: title of window
+- **n**: name
+- **r**: role
+- **c**: class
+
+*len*: maximum field length (0 for auto-size). If length is negative, the entry
+will be unchanged. If length is positive, the entry will be truncated or padded
+to fill that length.
+
+default: {w}  {c}   {t}
+
+`-window-command` *cmd*
+
+Set command to execute on selected window for an alt action (`-kb-accept-alt`).
+See *PATTERN*.
+
+Default: *"wmctrl -i -R {window}"*
+
+`-window-thumbnail`
+
+Show window thumbnail (if available) as icon in the window switcher.
+
+You can stop rofi from exiting when closing a window (allowing multiple to be
+closed in a row).
+
+```css
+configuration {
+  window {
+      close-on-delete: false;
+  }
+}
+```
+You can hide the currently active window with the 'hide-active-window' setting:
+
+```css
+configuration {
+  window {
+      hide-active-window: true;
+  }
+}
+```
+
+or pass `-window-hide-active-window true` on command line.
+
+You can prefer the icon theme above the window set icon with the
+'prefer-icon-theme' setting:
+
+```css
+configuration {
+  window {
+      prefer-icon-theme: true;
+  }
+}
+```
+
+or pass `-window-prefer-icon-theme true` on command line.
+
+### Combi settings
+
+`-combi-modes ` *mode1*,*mode2*
+
+The modes to combine in combi mode.
+For syntax to `-combi-modes`, see `-modes`.
+To get one merge view, of `window`,`run`, and `ssh`:
+
+```bash
+    rofi -show combi -combi-modes "window,run,ssh" -modes combi
+```
+
+**NOTE**: The i3 window manager dislikes commas in the command when specifying
+an exec command. For that case, `#` can be used as a separator.
+
+`-combi-display-format`
+
+The format string for entries in the `combi` dialog:
+
+- **mode**: the mode display name
+- **text**: the entry text
+
+Pango markup can be used to formatting the output.
+
+Default: {mode} {text}
+
+Note: This setting is ignored if `combi-hide-mode-prefix` is enabled.
+
+### History
+
+`-[no-]disable-history`
+
+Disable or re-enable history
+
+`-max-history-size` *number*
+
+Maximum number of entries to store in history. Defaults to 25. (WARNING: can
+cause slowdowns when set too high)
+
+### Message dialog
+
+`-e` *message*
+
+Pops up a message dialog (used internally for showing errors) with *message*.
+Message can be multi-line.
+
+Passing `-e -` reads (blocking) from standard in and displays this.
+
+### File browser settings
+
+File browser behavior can be controlled via the following options:
+
+```css
+configuration {
+   filebrowser {
+      /** Directory the file browser starts in. */
+      directory: "/some/directory";
+      /**
+        * Sorting method. Can be set to:
+        *   - "name"
+        *   - "mtime" (modification time)
+        *   - "atime" (access time)
+        *   - "ctime" (change time)
+        */
+      sorting-method: "name";
+      /** Group directories before files. */
+      directories-first: true;
+      /** Show hidden files. */
+      show-hidden: false;
+      /** return 1 on cancel. */
+      cancel-returns-1: true;
+      /** command */
+      command: "xdg-open";
+   }
+}
+```
+
+These options can also be passed on the commandline, for example:
+
+```bash
+rofi -filebrowser-cancel-returns-1 true -show filebrowser
+```
+
+The `show-hidden` can also be triggered with the `kb-delete-entry` keybinding.
+
+### Recursive Browser settings
+
+Recursive file browser behavior can be controlled via the following options:
+
+```css
+configuration {
+   recursivebrowser {
+      /** Directory the file browser starts in. */
+      directory: "/some/directory";
+      /** return 1 on cancel. */
+      cancel-returns-1: true;
+      /** filter entries using regex */
+      filter-regex: "(.*cache.*|.*\.o)";
+      /** command */
+      command: "xdg-open";
+   }
+}
+```
+
+### Entry history
+
+The number of previous inputs for the entry box can be modified by setting
+max-history on the entry box.
+
+```css
+configuration {
+    entry  {
+        max-history: 30;
+    }
+}
+```
+
+By default the file is stored in the systems cache directory, in a file called
+`rofi-entry-history.txt`.
+
+### Other
+
+`-drun-use-desktop-cache`
+
+Build and use a cache with the content of desktop files. Usable for systems
+with slow hard drives.
+
+`-drun-reload-desktop-cache`
+
+If `drun-use-desktop-cache` is enabled, rebuild a cache with the content of
+desktop files.
+
+`-drun-url-launcher` *command*
+
+Command to open a Desktop Entry that is a Link.
+
+`-pid` *path*
+
+Make **rofi** create a pid file and check this on startup. The pid file
+prevents multiple **rofi** instances from running simultaneously. This is
+useful when running **rofi** from a key-binding daemon.
+
+`-replace`
+
+If rofi is already running, based on pid file, try to kill that instance.
+
+`-display-{mode}` *string*
+
+Set the name to use for mode. This is used as prompt and in combi-browser.
+
+It is now preferred to use the configuration file:
+
+```css
+configuration {
+  {mode} {
+    display-name: *string*;
+  }
+}
+```
+
+`-[no-]click-to-exit`
+
+Click the mouse outside the **rofi** window to exit.
+
+Default: *enabled*
+
+`-xserver-i300-workaround`
+
+Workaround for bug in Xserver. See issue #611 and #1642 on the rofi issue
+tracker.
+
+Default: *disabled*
+
+## PATTERN
+
+To launch commands (for example, when using the ssh launcher), the user can
+enter the used command-line. The following keys can be used that will be
+replaced at runtime:
+
+- `{host}`: the host to connect to
+- `{terminal}`: the configured terminal (see -terminal)
+- `{ssh-client}`: the configured ssh client (see -ssh-client)
+- `{cmd}`: the command to execute
+- `{window}`: the window ID of the selected window (in `window-command`)
+
+It processes the string as follows: `{key}`
+is replaced by its value, if `{key}` is not set it is removed. If the `{key}`
+is in between `[]`  all the text between `[]` is removed if `{key}` is not set.
+Otherwise key is replaced and the `[]` are removed.
+
+For example: `{ssh-client} [-p {port}] {host}`
+
+## THEMING
+
+Please see **rofi-theme(5)** manpage for more information on theming.
+
+## KEY BINDINGS
+
+Please see the **rofi-keys(5)** manpage for the keybindings and how to set them
+up.
+
+The keybinding can also be used for actions, when the action is executed the
+mentioned keystroke is inserted:
+
+### Timeout
+
+You can configure an action to be taken when rofi has not been interacted
+with for a certain amount of seconds. You can specify a keybinding to trigger
+after X seconds.
+
+```css
+configuration {
+  timeout {
+      delay:  15;
+      action: "kb-cancel";
+  }
+}
+```
+
+### Input change
+
+When the input of the textbox changes:
+
+```css
+configuration {
+  inputchange {
+      action: "kb-row-first";
+  }
+}
+```
+
+## Available Modes
+
+### window
+
+Show a list of all the windows and allow switching between them. Pressing the
+`delete-entry` binding (`shift-delete`) will close the window. Pressing the
+`accept-custom` binding (`control-enter` or `shift-enter`) will run a command
+on the window. (See option `window-command` );
+
+If there is no match, it will try to launch the input.
+
+### windowcd
+
+Shows a list of the windows on the current desktop and allows switching between
+them. Pressing the `delete-entry` binding (`shift-delete`) will kill the
+window. Pressing the `accept-custom` binding (`control-enter` or `shift-enter`)
+will run a command on the window. (See option `window-command` );
+
+If there is no match, it will try to launch the input.
+
+### run
+
+Shows a list of executables in `$PATH` and can launch them (optional in a
+terminal).
+
+-   Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
+    from the run history.
+
+-   Pressing the `accept-custom` binding (`control-enter`) will run the command
+    as entered in the entry box.
+
+-   Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
+    terminal.
+
+When pressing the `mode-complete` binding (`Control-l`), you can use the File
+Browser mode to launch the application with a file as the first argument.
+
+### drun
+
+Same as the **run** launches, but the list is created from the installed
+desktop files. It automatically launches them in a terminal if specified in the
+Desktop File.
+
+-   Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
+    from the run history.
+
+-   Pressing the `accept-custom` binding (`control-enter`) will run the command
+    as entered in the entry box.
+
+-   Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
+    terminal.
+
+When pressing the `mode-complete` binding (`Control-l`), you can use the File
+Browser mode to launch the application passing a file as argument if specified
+in the desktop file.
+
+The DRUN mode tries to follow the [XDG Desktop Entry
+Specification](https://freedesktop.org/wiki/Specifications/desktop-entry-spec/)
+and should be compatible with applications using this standard.  Some
+applications create invalid desktop files, **rofi** will discard these entries.
+See the debugging section for more info on DRUN mode, this will print why
+desktop files are discarded.
+
+There are a few advanced options to tweak the behaviour:
+
+```css
+configuration {
+   drun {
+      /** Scan the current users desktop for desktop files. */
+      scan-desktop: true;
+      /** Parse user desktop files. */
+      parse-user:   true;
+      /** Parse system desktop files. */
+      parse-system: false;
+   }
+}
+```
+### ssh
+
+Shows a list of SSH targets based on your `ssh` config file, and allows to
+quickly `ssh` into them.
+
+### keys
+
+Shows a searchable list of key bindings.
+
+### script
+
+Allows custom scripted Modes to be added, see the **rofi-script(5)** manpage
+for more information.
+
+### combi
+
+Combines multiple modes in one list. Specify which modes are included with the
+`-combi-modes` option.
+
+When using the combi mode, a *!bang* can be used to filter the results by modes.
+All modes that match the bang as a prefix are included.
+For example, say you have specified `-combi-modes run,window,windowcd`. If your
+query begins with the bang `!w`, only results from the `window` and `windowcd`
+modes are shown, even if the rest of the input text would match results from `run`.
+
+If no match, the input is handled by the first combined modes.
+
+## FAQ
+
+### The text in the window switcher is not nicely aligned
+
+Try using a mono-space font or tabs + the tab-stops setting..
+
+### The window is completely black
+
+Check quotes used on the command-line: you might have used `“` ("smart quotes")
+instead of `"` ("machine quotes").
+
+### What does the icon in the top right show?
+
+The indicator shows:
+
+- ` ` Case insensitive and no sorting.
+- `-` Case sensitivity enabled, no sorting.
+- `+` Case insensitive and Sorting enabled
+- `±` Sorting and Case sensitivity enabled"
+
+### Why do I see different icons for run,drun and window mode
+
+Each of these modes uses different methods of resolving the icon:
+
+-   Window: It first uses the icon that the application exposes via the X11
+    Server, if none is set it does a lookup of the window Class name in the icon
+    theme.
+
+-   drun: It uses the icon set in the desktop file.
+
+-   run: It does a lookup using the executable name.
+
+## EXAMPLES
+
+Some basic usage examples of **rofi**:
+
+Show the run dialog:
+
+```bash
+    rofi -modes run -show run
+```
+
+Show the run dialog, and allow switching to Desktop File run dialog (`drun`):
+
+```bash
+    rofi -modes run,drun -show run
+```
+
+Combine the run and Desktop File run dialog (`drun`):
+
+```bash
+    rofi -modes combi -show combi -combi-modes run,drun
+```
+
+Combine the run and Desktop File run dialog (`drun`), and allow switching to
+window switcher:
+
+```bash
+    rofi -modes combi,window -show combi -combi-modes run,drun
+```
+
+Pop up a text message claiming that this is the end:
+
+```bash
+    rofi -e "This is the end"
+```
+
+Pop up a text message in red, bold font claiming that this is still the end:
+
+```bash
+    rofi -e "<span color='red'><b>This is still the end</b></span>" -markup
+```
+
+Show all key bindings:
+
+```bash
+    rofi -show keys
+```
+
+## i3
+
+In [i3](http://i3wm.org/) you want to bind **rofi** to be launched on key
+release. Otherwise, it cannot grab the keyboard. See also the i3
+[manual](http://i3wm.org/docs/userguide.html):
+
+Some tools (such as `import` or `xdotool`) might be unable to run upon a
+KeyPress event, because the keyboard/pointer is still grabbed. For these
+situations, the `--release` flag can be used, as it will execute the command
+after the keys have been released.
+
+## LICENSE
+
+```text
+    MIT/X11
+
+    Permission is hereby granted, free of charge, to any person obtaining
+    a copy of this software and associated documentation files (the
+    "Software"), to deal in the Software without restriction, including
+    without limitation the rights to use, copy, modify, merge, publish,
+    distribute, sublicense, and/or sell copies of the Software, and to
+    permit persons to whom the Software is furnished to do so, subject to
+    the following conditions:
+
+    The above copyright notice and this permission notice shall be
+    included in all copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+    OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+    MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+    IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+    CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+    TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+    SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+```
+
+## WEBSITE
+
+**rofi** website can be found [here](https://github.com/davatorium/rofi/)
+
+## SUPPORT
+
+**rofi** support can be obtained:
+
+- [GitHub Discussions](https://github.com/davatorium/rofi/discussions)
+- [IRC](irc://irc.libera.chat:6697/#rofi) (#rofi on irc.libera.chat),
+
+## DEBUGGING
+
+For more information see **rofi-debugging(5)** manpage. 
+
+## ISSUE TRACKER
+
+The **rofi** issue tracker can be found [here](https://github.com/davatorium/rofi/issues)
+Before creating an issue, consider posting a question on the [discussion forum](https://github.com/davatorium/rofi/discussions) first.
+When creating an issue, please read [this](https://github.com/davatorium/rofi/blob/master/.github/CONTRIBUTING.md)
+first.
+
+## SEE ALSO
+
+**rofi-sensible-terminal(1)**, **dmenu(1)**, **rofi-debugging(5)**,
+**rofi-theme(5)**, **rofi-script(5)**,
+**rofi-keys(5)**,**rofi-theme-selector(1)**,**rofi-dmenu(5)**
+
+## AUTHOR
+
+- Qball Cow <qball@blame.services>
+- Rasmus Steinke <rasi@xssn.at>
+- Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: [Sean Pringle](https://github.com/seanpringle/simpleswitcher) <sean.pringle@gmail.com>
+
+For a full list of authors, check the `AUTHORS` file.
diff --git a/mkdocs/docs/1.7.7/rofi-debugging.5.markdown b/mkdocs/docs/1.7.7/rofi-debugging.5.markdown
new file mode 100644
index 000000000..4df15d529
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-debugging.5.markdown
@@ -0,0 +1,177 @@
+# rofi-debugging(5)
+
+## NAME
+
+Debugging rofi.
+
+When reporting an issue with rofi crashing, or misbehaving. It helps to do some
+small test to help pin-point the problem.
+
+First try disabling your custom configuration: `-no-config`
+
+This disables the parsing of the configuration files. This runs rofi in *stock*
+mode.
+
+If you run custom C plugins, you can disable the plugins using: `-no-plugins`
+
+## Get the relevant information for an issue
+
+Please pastebin the output of the following commands:
+
+```bash
+rofi -help
+rofi -dump-config
+rofi -dump-theme
+```
+
+`rofi -help`  provides us with the configuration files parsed, the exact
+version, monitor layout and more useful information.
+
+The `rofi -dump-config` and `rofi -dump-theme` output gives us `rofi`
+interpretation of your configuration and theme.
+
+Please check the output for identifiable information and remove this.
+
+## Timing traces
+
+To get a timing trace, enable the **Timings** debug domain.
+
+```bash
+G_MESSAGES_DEBUG=Timings rofi -show drun
+```
+It will show a trace with (useful) timing information at relevant points during
+the execution. This will help debugging when rofi is slow to start.
+
+Example trace:
+
+```text
+(process:14942): Timings-DEBUG: 13:47:39.335: 0.000000 (0.000000): Started
+(process:14942): Timings-DEBUG: 13:47:39.335: 0.000126 (0.000126): ../source/rofi.c:main:786 
+(process:14942): Timings-DEBUG: 13:47:39.335: 0.000163 (0.000037): ../source/rofi.c:main:819 
+(process:14942): Timings-DEBUG: 13:47:39.336: 0.000219 (0.000056): ../source/rofi.c:main:826 Setup Locale
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001235 (0.001016): ../source/rofi.c:main:828 Collect MODI
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001264 (0.000029): ../source/rofi.c:main:830 Setup MODI
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001283 (0.000019): ../source/rofi.c:main:834 Setup mainloop
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001369 (0.000086): ../source/rofi.c:main:837 NK Bindings
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001512 (0.000143): ../source/xcb.c:display_setup:1177 Open Display
+(process:14942): Timings-DEBUG: 13:47:39.337: 0.001829 (0.000317): ../source/xcb.c:display_setup:1192 Setup XCB
+(process:14942): Timings-DEBUG: 13:47:39.346: 0.010650 (0.008821): ../source/rofi.c:main:844 Setup Display
+(process:14942): Timings-DEBUG: 13:47:39.346: 0.010715 (0.000065): ../source/rofi.c:main:848 Setup abe
+(process:14942): Timings-DEBUG: 13:47:39.350: 0.015101 (0.004386): ../source/rofi.c:main:883 Load cmd config 
+(process:14942): Timings-DEBUG: 13:47:39.351: 0.015275 (0.000174): ../source/rofi.c:main:907 Setup Modi
+(process:14942): Timings-DEBUG: 13:47:39.351: 0.015291 (0.000016): ../source/view.c:rofi_view_workers_initialize:1922 Setup Threadpool, start
+(process:14942): Timings-DEBUG: 13:47:39.351: 0.015349 (0.000058): ../source/view.c:rofi_view_workers_initialize:1945 Setup Threadpool, done
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032018 (0.016669): ../source/rofi.c:main:1000 Setup late Display
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032080 (0.000062): ../source/rofi.c:main:1003 Theme setup
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032109 (0.000029): ../source/rofi.c:startup:668 Startup
+(process:14942): Timings-DEBUG: 13:47:39.367: 0.032121 (0.000012): ../source/rofi.c:startup:677 Grab keyboard
+(process:14942): Timings-DEBUG: 13:47:39.368: 0.032214 (0.000093): ../source/view.c:__create_window:701 xcb create window
+(process:14942): Timings-DEBUG: 13:47:39.368: 0.032235 (0.000021): ../source/view.c:__create_window:705 xcb create gc
+(process:14942): Timings-DEBUG: 13:47:39.368: 0.033136 (0.000901): ../source/view.c:__create_window:714 create cairo surface
+(process:14942): Timings-DEBUG: 13:47:39.369: 0.033286 (0.000150): ../source/view.c:__create_window:723 pango cairo font setup
+(process:14942): Timings-DEBUG: 13:47:39.369: 0.033351 (0.000065): ../source/view.c:__create_window:761 configure font
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045896 (0.012545): ../source/view.c:__create_window:769 textbox setup
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045944 (0.000048): ../source/view.c:__create_window:781 setup window attributes
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045955 (0.000011): ../source/view.c:__create_window:791 setup window fullscreen
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045966 (0.000011): ../source/view.c:__create_window:797 setup window name and class
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045974 (0.000008): ../source/view.c:__create_window:808 setup startup notification
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045981 (0.000007): ../source/view.c:__create_window:810 done
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045992 (0.000011): ../source/rofi.c:startup:679 Create Window
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.045999 (0.000007): ../source/rofi.c:startup:681 Parse ABE
+(process:14942): Timings-DEBUG: 13:47:39.381: 0.046113 (0.000114): ../source/rofi.c:startup:684 Config sanity check
+(process:14942): Timings-DEBUG: 13:47:39.384: 0.048229 (0.002116): ../source/dialogs/run.c:get_apps:216 start
+(process:14942): Timings-DEBUG: 13:47:39.390: 0.054626 (0.006397): ../source/dialogs/run.c:get_apps:336 stop
+(process:14942): Timings-DEBUG: 13:47:39.390: 0.054781 (0.000155): ../source/dialogs/drun.c:get_apps:634 Get Desktop apps (start)
+(process:14942): Timings-DEBUG: 13:47:39.391: 0.055264 (0.000483): ../source/dialogs/drun.c:get_apps:641 Get Desktop apps (user dir)
+(process:14942): Timings-DEBUG: 13:47:39.418: 0.082884 (0.027620): ../source/dialogs/drun.c:get_apps:659 Get Desktop apps (system dirs)
+(process:14942): Timings-DEBUG: 13:47:39.418: 0.082944 (0.000060): ../source/dialogs/drun.c:get_apps_history:597 Start drun history
+(process:14942): Timings-DEBUG: 13:47:39.418: 0.082977 (0.000033): ../source/dialogs/drun.c:get_apps_history:617 Stop drun history
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083638 (0.000661): ../source/dialogs/drun.c:get_apps:664 Sorting done.
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083685 (0.000047): ../source/view.c:rofi_view_create:1759 
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083700 (0.000015): ../source/view.c:rofi_view_create:1783 Startup notification
+(process:14942): Timings-DEBUG: 13:47:39.419: 0.083711 (0.000011): ../source/view.c:rofi_view_create:1786 Get active monitor
+(process:14942): Timings-DEBUG: 13:47:39.420: 0.084693 (0.000982): ../source/view.c:rofi_view_refilter:1028 Filter start
+(process:14942): Timings-DEBUG: 13:47:39.421: 0.085992 (0.001299): ../source/view.c:rofi_view_refilter:1132 Filter done
+(process:14942): Timings-DEBUG: 13:47:39.421: 0.086090 (0.000098): ../source/view.c:rofi_view_update:982 
+(process:14942): Timings-DEBUG: 13:47:39.421: 0.086123 (0.000033): ../source/view.c:rofi_view_update:1002 Background
+(process:14942): Timings-DEBUG: 13:47:39.428: 0.092864 (0.006741): ../source/view.c:rofi_view_update:1008 widgets
+```
+
+## Debug domains
+
+To further debug the plugin, you can get a trace with (lots of) debug
+information. This debug output can be enabled for multiple parts in rofi using
+the glib debug framework. Debug domains can be enabled by setting the
+G\_MESSAGES\_DEBUG environment variable. At the time of creation of this page,
+the following debug domains exist:
+
+- all: Show debug information from all domains.
+- X11Helper: The X11 Helper functions.
+- View: The main window view functions.
+- Widgets.Box: The Box widget.
+- Modes.DMenu: The dmenu mode.
+- Modes.Run: The run mode.
+- Modes.DRun: The desktop file run mode.
+- Modes.Window: The window mode.
+- Modes.Script: The script mode.
+- Modes.Combi: The script mode.
+- Modes.Ssh: The ssh mode.
+- Rofi: The main application.
+- Timings: Get timing output.
+- Theme: Theme engine debug output. (warning lots of output).
+- Widgets.Icon: The Icon widget.
+- Widgets.Box: The box widget.
+- Widgets.Container: The container widget.
+- Widgets.Window: The window widget.
+- Helpers.IconFetcher: Information about icon lookup.
+
+For full list see `man rofi`.
+
+Example: `G_MESSAGES_DEBUG=Dialogs.DRun rofi -show drun` To get specific output
+from the Desktop file run dialog.
+
+To redirect the debug output to a file (`~/rofi.log`) add:
+
+```bash
+rofi -show drun -log ~/rofi.log
+```
+
+Specifying the logfile automatically enabled all log domains.
+This can be useful when rofi is launched from a window manager.
+
+## Creating a backtrace
+
+First make sure you compile **rofi** with debug symbols:
+
+```bash
+make CFLAGS="-O0 -g3" clean rofi
+```
+
+Getting a backtrace using GDB is not very handy. Because if rofi get stuck, it
+grabs keyboard and mouse. So if it crashes in GDB you are stuck. The best way
+to go is to enable core file. (ulimit -c unlimited in bash) then make rofi
+crash. You can then load the core in GDB.
+
+```bash
+gdb rofi core
+```
+
+Then type inside gdb:
+
+```bash
+thread apply all bt
+```
+
+The output trace is useful when reporting crashes.
+
+Some distribution have `systemd-coredump`, this way you can easily get a
+backtrace via `coredumpctl`.
+
+## SEE ALSO
+
+rofi-sensible-terminal(1), dmenu(1), rofi-theme(5),
+rofi-script(5), rofi-keys(5),rofi-theme-selector(1)
+
+## AUTHOR
+
+* Qball Cow <qball@blame.services>
diff --git a/mkdocs/docs/1.7.7/rofi-dmenu.5.markdown b/mkdocs/docs/1.7.7/rofi-dmenu.5.markdown
new file mode 100644
index 000000000..27e484b3f
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-dmenu.5.markdown
@@ -0,0 +1,245 @@
+# rofi-dmenu(5)
+
+## NAME
+
+**rofi dmenu mode** - Rofi dmenu emulation
+
+## DESCRIPTION
+
+To integrate **rofi** into scripts as simple selection dialogs, 
+**rofi** supports emulating **dmenu(1)** (A dynamic menu for X11).
+
+The website for `dmenu` can be found [here](http://tools.suckless.org/dmenu/).
+
+**rofi** does not aim to be 100% compatible with `dmenu`. There are simply too
+many flavors of `dmenu`. The idea is that the basic usage command-line flags
+are obeyed, theme-related flags are not. Besides, **rofi** offers some extended
+features (like multi-select, highlighting, message bar, extra key bindings).
+
+## BASIC CONCEPT
+
+In `dmenu` mode, **rofi** reads data from standard in, splits them into
+separate entries and displays them. If the user selects a row, this is printed
+out to standard out, allowing the script to process it further.
+
+By default separation of rows is done on new lines, making it easy to pipe the
+output a one application into **rofi** and the output of rofi into the next.
+
+## USAGE 
+
+By launching **rofi** with the `-dmenu` flag it will go into dmenu emulation
+mode.
+
+```bash
+ls | rofi -dmenu
+```
+
+### DMENU DROP-IN REPLACEMENT
+
+If `argv[0]` (calling command) is dmenu, **rofi** will start in dmenu mode.
+This way, it can be used as a drop-in replacement for dmenu. Just copy or
+symlink **rofi** to dmenu in `$PATH`.
+
+```bash
+ln -s /usr/bin/rofi /usr/bin/dmenu
+```
+
+### DMENU VS SCRIPT MODE
+
+Script mode is used to extend **rofi**, dmenu mode is used to extend a script.
+The two do share much of the same input format. Please see the
+**rofi-script(5)** manpage for more information.
+
+### DMENU SPECIFIC COMMANDLINE FLAGS
+
+A lot of these options can also be modified by the script using special input.
+See the **rofi-script(5)** manpage for more information about this syntax.
+
+`-sep` *separator*
+
+Separator for `dmenu`. Example: To show a list of 'a' to 'e' with '|' as a
+separator:
+
+```bash
+echo "a|b|c|d|e" | rofi -sep '|' -dmenu
+```
+
+`-p` *prompt*
+
+Specify the prompt to show in `dmenu` mode. For example, select 'monkey',
+a,b,c,d, or e.
+
+```bash
+echo "a|b|c|d|e" | rofi -sep '|' -dmenu -p "monkey"
+```
+
+Default: *dmenu*
+
+`-l` *number of lines to show*
+
+Maximum number of lines the menu may show before scrolling.
+
+```bash
+rofi -dmenu -l 25
+```
+
+Default: *15*
+
+`-i`
+
+Makes `dmenu` searches case-insensitive
+
+`-a` *X*
+
+Active row, mark *X* as active. Where *X* is a comma-separated list of
+python(1)-style indices and ranges, e.g.  indices start at 0, -1 refers to the
+last row with -2 preceding it, ranges are left-open and right-close, and so on.
+You can specify:
+
+- A single row: '5'
+- A range of (last 3) rows: '-3:'
+- 4 rows starting from row 7: '7:11' (or in legacy notation: '7-10')
+- A set of rows: '2,0,-9'
+- Or any combination: '5,-3:,7:11,2,0,-9'
+
+`-u` *X*
+
+Urgent row, mark *X* as urgent. See `-a` option for details.
+
+`-only-match`
+
+Only return a selected item, do not allow custom entry.
+This mode always returns an entry. It will not return if no matching entry is
+selected.
+
+`-no-custom`
+
+Only return a selected item, do not allow custom entry.
+This mode returns directly when no entries given.
+
+`-format` *format*
+
+Allows the output of dmenu to be customized (N is the total number of input
+entries):
+
+- 's' selected string
+- 'i' index (0 - (N-1))
+- 'd' index (1 - N)
+- 'q' quote string
+- 'p' Selected string stripped from Pango markup (Needs to be a valid string)
+- 'f' filter string (user input)
+- 'F' quoted filter string (user input)
+
+Default: 's'
+
+`-select` *string*
+
+Select first line that matches the given string
+
+`-mesg` *string*
+
+Add a message line below the filter entry box. Supports Pango markup. For more
+information on supported markup, see
+[here](https://docs.gtk.org/Pango/pango_markup.html)
+
+`-dump`
+
+Dump the filtered list to stdout and quit.
+This can be used to get the list as **rofi** would filter it.
+Use together with `-filter` command.
+
+`-input` *file*
+
+Reads from *file* instead of stdin.
+
+`-password`
+
+Hide the input text. This should not be considered secure!
+
+`-markup-rows`
+
+Tell **rofi** that DMenu input is Pango markup encoded, and should be rendered.
+See [here](https://developer.gnome.org/pygtk/stable/pango-markup-language.html)
+for details about Pango markup.
+
+`-multi-select`
+
+Allow multiple lines to be selected. Adds a small selection indicator to the
+left of each entry.
+
+`-sync`
+
+Force **rofi** mode to first read all data from stdin before showing the
+selection window. This is original dmenu behavior.
+
+Note: the default asynchronous mode will also be automatically disabled if used
+with conflicting options,
+such as `-dump`, `-only-match` or `-auto-select`.
+
+`-window-title` *title*
+
+Set name used for the window title. Will be shown as Rofi - *title*
+
+`-w` *windowid*
+
+Position **rofi** over the window with the given X11 window ID.
+
+`-keep-right`
+
+Set ellipsize mode to start. So, the end of the string is visible.
+
+`-display-columns`
+
+A comma seperated list of columns to show.
+
+`-display-column-separator`
+
+The column separator. This is a regex. 
+
+*default*: '\t'
+
+`-ballot-selected-str` *string*
+
+When multi-select is enabled, prefix this string when element is selected.
+
+*default*: "☑ "
+
+`-ballot-unselected-str` *string*
+
+When multi-select is enabled, prefix this string when element is not selected.
+
+*default*: "☐ "
+
+`-ellipsize-mode` (start|middle|end)
+
+Set ellipsize mode on the listview.
+
+*default* "end"
+
+## PARSING ROW OPTIONS
+
+Extra options for individual rows can be also set. See the **rofi-script(5)**
+manpage for details; the syntax and supported features are identical.
+
+## RETURN VALUE
+
+- **0**: Row has been selected accepted by user.
+- **1**: User cancelled the selection.
+- **10-28**: Row accepted by custom keybinding.
+
+## SEE ALSO
+
+rofi(1), rofi-sensible-terminal(1), dmenu(1), rofi-theme(5), rofi-script(5),
+rofi-theme-selector(1), ascii(7)
+
+## AUTHOR
+
+Qball Cow <qball@gmpclient.org>
+
+Rasmus Steinke <rasi@xssn.at>
+
+Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: Sean Pringle <sean.pringle@gmail.com>
+
+For a full list of authors, check the AUTHORS file.
diff --git a/mkdocs/docs/1.7.7/rofi-keys.5.markdown b/mkdocs/docs/1.7.7/rofi-keys.5.markdown
new file mode 100644
index 000000000..8aeefacc2
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-keys.5.markdown
@@ -0,0 +1,576 @@
+# rofi-keys(5)
+
+## NAME
+
+**rofi keys** - Rofi Key and Mouse bindings
+
+## DESCRIPTION
+
+**rofi** supports overriding of any of it key and mouse binding.
+
+## Setting binding
+
+Bindings can be done on the commandline (-{bindingname}):
+
+```bash
+rofi -show run -kb-accept-entry 'Control+Shift+space'
+```
+
+or via the configuration file:
+
+```css
+configuration {
+  kb-accept-entry: "Control+Shift+space";
+}
+```
+
+The key can be set by its name (see above) or its keycode:
+
+```css
+configuration {
+  kb-accept-entry: "Control+Shift+[65]";
+}
+```
+
+An easy way to look up keycode is xev(1).
+
+Multiple keys can be specified for an action as a comma separated list:
+
+```css
+configuration {
+  kb-accept-entry: "Control+Shift+space,Return";
+}
+```
+
+By Default **rofi** reacts on pressing, to act on the release of all keys
+prepend the binding with `!`:
+
+```css
+configuration {
+  kb-accept-entry: "!Control+Shift+space,Return";
+}
+```
+
+## Unsetting a binding
+
+To unset a binding, pass an empty string.
+
+```css
+configuration {
+  kb-clear-line: "";
+}
+```
+
+## Keyboard Bindings
+
+`kb-primary-paste`
+
+Paste primary selection
+
+Default:  Control+V,Shift+Insert
+
+`kb-secondary-paste`
+
+Paste clipboard
+
+Default:  Control+v,Insert
+
+`kb-secondary-copy`
+
+Copy current selection to clipboard
+
+Default:  Control+c
+
+`kb-clear-line`
+
+Clear input line
+
+Default:  Control+w
+
+`kb-move-front`
+
+Beginning of line
+
+Default:  Control+a
+
+`kb-move-end`
+
+End of line
+
+Default:  Control+e
+
+`kb-move-word-back`
+
+Move back one word
+
+Default:  Alt+b,Control+Left
+
+`kb-move-word-forward`
+
+Move forward one word
+
+Default:  Alt+f,Control+Right
+
+`kb-move-char-back`
+
+Move back one char
+
+Default:  Left,Control+b
+
+`kb-move-char-forward`
+
+Move forward one char
+
+Default:  Right,Control+f
+
+`kb-remove-word-back`
+
+Delete previous word
+
+Default:  Control+Alt+h,Control+BackSpace
+
+`kb-remove-word-forward`
+
+Delete next word
+
+Default:  Control+Alt+d
+
+`kb-remove-char-forward`
+
+Delete next char
+
+Default:  Delete,Control+d
+
+`kb-remove-char-back`
+
+Delete previous char
+
+Default:  BackSpace,Shift+BackSpace,Control+h
+
+`kb-remove-to-eol`
+
+Delete till the end of line
+
+Default:  Control+k
+
+`kb-remove-to-sol`
+
+Delete till the start of line
+
+Default:  Control+u
+
+`kb-accept-entry`
+
+Accept entry
+
+Default:  Control+j,Control+m,Return,KP\_Enter
+
+`kb-accept-custom`
+
+Use entered text as command (in ssh/run modes)
+
+Default:  Control+Return
+
+`kb-accept-custom-alt`
+
+Use entered text as command (in ssh/run modes)
+
+Default:  Control+Shift+Return
+
+`kb-accept-alt`
+
+Use alternate accept command.
+
+Default:  Shift+Return
+
+`kb-delete-entry`
+
+Delete entry from history
+
+Default:  Shift+Delete
+
+`kb-mode-next`
+
+Switch to the next mode.
+
+Default:  Shift+Right,Control+Tab
+
+`kb-mode-previous`
+
+Switch to the previous mode.
+
+Default:  Shift+Left,Control+ISO\_Left\_Tab
+
+`kb-mode-complete`
+
+Start completion for mode.
+
+Default:  Control+l
+
+`kb-row-left`
+
+Go to the previous column
+
+Default:  Control+Page\_Up
+
+`kb-row-right`
+
+Go to the next column
+
+Default:  Control+Page\_Down
+
+`kb-row-up`
+
+Select previous entry
+
+Default:  Up,Control+p
+
+`kb-row-down`
+
+Select next entry
+
+Default:  Down,Control+n
+
+`kb-row-tab`
+
+Go to next row, if one left, accept it, if no left next mode.
+
+Default:
+
+`kb-element-next`
+
+Go to next row.
+
+Default: Tab
+
+`kb-element-prev`
+
+Go to previous row.
+
+Default: ISO\_Left\_Tab
+
+`kb-page-prev`
+
+Go to the previous page
+
+Default:  Page\_Up
+
+`kb-page-next`
+
+Go to the next page
+
+Default:  Page\_Down
+
+`kb-row-first`
+
+Go to the first entry
+
+Default:  Home,KP\_Home
+
+`kb-row-last`
+
+Go to the last entry
+
+Default:  End,KP\_End
+
+`kb-row-select`
+
+Set selected item as input text
+
+Default:  Control+space
+
+`kb-screenshot`
+
+Take a screenshot of the rofi window
+
+Default:  Alt+S
+
+`kb-ellipsize`
+
+Toggle between ellipsize modes for displayed data
+
+Default:  Alt+period
+
+`kb-toggle-case-sensitivity`
+
+Toggle case sensitivity
+
+Default:  grave,dead\_grave
+
+`kb-toggle-sort`
+
+Toggle filtered menu sort
+
+Default:  Alt+grave
+
+`kb-cancel`
+
+Quit rofi
+
+Default:  Escape,Control+g,Control+bracketleft
+
+`kb-custom-1`
+
+Custom keybinding 1
+
+Default:  Alt+1
+
+`kb-custom-2`
+
+Custom keybinding 2
+
+Default:  Alt+2
+
+`kb-custom-3`
+
+Custom keybinding 3
+
+Default:  Alt+3
+
+`kb-custom-4`
+
+Custom keybinding 4
+
+Default:  Alt+4
+
+`kb-custom-5`
+
+Custom Keybinding 5
+
+Default:  Alt+5
+
+`kb-custom-6`
+
+Custom keybinding 6
+
+Default:  Alt+6
+
+`kb-custom-7`
+
+Custom Keybinding 7
+
+Default:  Alt+7
+
+`kb-custom-8`
+
+Custom keybinding 8
+
+Default:  Alt+8
+
+`kb-custom-9`
+
+Custom keybinding 9
+
+Default:  Alt+9
+
+`kb-custom-10`
+
+Custom keybinding 10
+
+Default:  Alt+0
+
+`kb-custom-11`
+
+Custom keybinding 11
+
+Default:  Alt+exclam
+
+`kb-custom-12`
+
+Custom keybinding 12
+
+Default:  Alt+at
+
+`kb-custom-13`
+
+Custom keybinding 13
+
+Default:  Alt+numbersign
+
+`kb-custom-14`
+
+Custom keybinding 14
+
+Default:  Alt+dollar
+
+`kb-custom-15`
+
+Custom keybinding 15
+
+Default:  Alt+percent
+
+`kb-custom-16`
+
+Custom keybinding 16
+
+Default:  Alt+dead\_circumflex
+
+`kb-custom-17`
+
+Custom keybinding 17
+
+Default:  Alt+ampersand
+
+`kb-custom-18`
+
+Custom keybinding 18
+
+Default:  Alt+asterisk
+
+`kb-custom-19`
+
+Custom Keybinding 19
+
+Default:  Alt+parenleft
+
+`kb-select-1`
+
+Select row 1
+
+Default:  Super+1
+
+`kb-select-2`
+
+Select row 2
+
+Default:  Super+2
+
+`kb-select-3`
+
+Select row 3
+
+Default:  Super+3
+
+`kb-select-4`
+
+Select row 4
+
+Default:  Super+4
+
+`kb-select-5`
+
+Select row 5
+
+Default:  Super+5
+
+`kb-select-6`
+
+Select row 6
+
+Default:  Super+6
+
+`kb-select-7`
+
+Select row 7
+
+Default:  Super+7
+
+`kb-select-8`
+
+Select row 8
+
+Default:  Super+8
+
+`kb-select-9`
+
+Select row 9
+
+Default:  Super+9
+
+`kb-select-10`
+
+Select row 10
+
+Default:  Super+0
+
+`kb-entry-history-up`
+
+Go up in the entry history.
+
+Default:    Control+Up
+
+`kb-entry-history-down`
+
+Go down in the entry history.
+
+Default:    Control+Down
+
+## Mouse Bindings
+
+`ml-row-left`
+
+Go to the previous column
+
+Default:  ScrollLeft
+
+`ml-row-right`
+
+Go to the next column
+
+Default:  ScrollRight
+
+`ml-row-up`
+
+Select previous entry
+
+Default:  ScrollUp
+
+`ml-row-down`
+
+Select next entry
+
+Default:  ScrollDown
+
+`me-select-entry`
+
+Select hovered row
+
+Default:  MousePrimary
+
+`me-accept-entry`
+
+Accept hovered row
+
+Default:  MouseDPrimary
+
+`me-accept-custom`
+
+Accept hovered row with custom action
+
+Default:  Control+MouseDPrimary
+
+## Mouse key bindings
+
+The following mouse buttons can be bound:
+
+* `Primary`: Primary (Left) mouse button click.
+* `Secondary`:  Secondary (Right) mouse button click.
+* `Middle`: Middle mouse button click.
+* `Forward`: The forward mouse button.
+* `Back`: The back mouse button.
+* `ExtraN`: The N'the mouse button. (Depending on mouse support).
+
+The Identifier is constructed as follow:
+
+`Mouse<D><Button>`
+
+* `D` indicates optional Double press.
+* `Button` is the button name.
+
+So `MouseDPrimary` is Primary (`Left`) mouse button double click.
+
+## SEE ALSO
+
+rofi(1), rofi-sensible-terminal(1), rofi-theme(5), rofi-script(5)
+
+## AUTHOR
+
+Qball Cow <qball@gmpclient.org>
+
+Rasmus Steinke <rasi@xssn.at>
+
+Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: Sean Pringle <sean.pringle@gmail.com>
+
+For a full list of authors, check the AUTHORS file.
diff --git a/mkdocs/docs/1.7.7/rofi-script.5.markdown b/mkdocs/docs/1.7.7/rofi-script.5.markdown
new file mode 100644
index 000000000..aeeac8fda
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-script.5.markdown
@@ -0,0 +1,216 @@
+# rofi-script(5)
+
+## NAME
+
+**rofi script mode** - Rofi format for scriptable mode.
+
+## DESCRIPTION
+
+**rofi** supports modes that use simple scripts in the background to generate a
+list and process the result from user actions.  This provide a simple interface
+to make simple extensions to rofi.
+
+## USAGE
+
+To specify a script mode, set a mode with the following syntax:
+"{name}:{executable}"
+
+For example:
+
+```bash
+rofi -show fb -modes "fb:file_browser.sh"
+```
+
+The name should be unique.
+
+## API
+
+Rofi calls the executable without arguments on startup.  This should generate a
+list of options, separated by a newline (`\n`) (This can be changed by the
+script). If the user selects an option, rofi calls the executable with the text
+of that option as the first argument. If the script returns no entries, rofi
+quits.
+
+A simple script would be:
+
+```bash
+#!/usr/bin/env bash
+
+if [ x"$@" = x"quit" ]
+then
+    exit 0
+fi
+echo "reload"
+echo "quit"
+
+```
+
+This shows two entries, reload and quit. When the quit entry is selected, rofi
+closes.
+
+## Environment
+
+Rofi sets the following environment variable when executing the script:
+
+### `ROFI_RETV`
+
+An integer number with the current state:
+
+- **0**: Initial call of script.
+- **1**: Selected an entry.
+- **2**: Selected a custom entry.
+- **10-28**: Custom keybinding 1-19 ( need to be explicitly enabled by script ).
+
+### `ROFI_INFO`
+
+Environment get set when selected entry get set with the property value of the
+'info' row option, if set.
+
+### `ROFI_DATA`
+
+Environment get set when script sets `data` option in header.
+
+## Passing mode options
+
+Extra options, like setting the prompt, can be set by the script. Extra options
+are lines that start with a NULL character (`\0`) followed by a key, separator
+(`\x1f`) and value.
+
+For example to set the prompt:
+
+```bash
+    echo -en "\0prompt\x1fChange prompt\n"
+```
+
+The following extra options exists:
+
+-   **prompt**:      Update the prompt text.
+
+-   **message**:     Update the message text.
+
+-   **markup-rows**: If 'true' renders markup in the row.
+
+-   **urgent**:      Mark rows as urgent. (for syntax see the urgent option in
+    dmenu mode)
+
+-   **active**:      Mark rows as active. (for syntax see the active option in
+    dmenu mode)
+
+-   **delim**:       Set the delimiter for for next rows. Default is '\n' and
+    this option should finish with this. Only call this on first call of script,
+    it is remembered for consecutive calls.
+
+-   **no-custom**:   If set to 'true'; only accept listed entries, ignore custom
+    input.
+
+-   **use-hot-keys**: If set to true, it enabled the Custom keybindings for
+    script. Warning this breaks the normal rofi flow.
+
+-   **keep-selection**: If set, the selection is not moved to the first entry,
+    but the current position is maintained. The filter is cleared.
+
+-   **keep-filter**: If set, the filter is not cleared. 
+
+-   **new-selection**: If `keep-selection` is set, this allows you to override
+    the selected entry (absolute position).
+
+-   **data**:         Passed data to the next execution of the script via
+    **ROFI\_DATA**.
+
+-   **theme**:       Small theme snippet to f.e. change the background color of
+    a widget.
+
+The **theme** property cannot change the interface while running, it is only
+usable for small changes in, for example background color, of widgets that get
+updated during display like the row color of the listview.
+
+## Parsing row options
+
+Extra options for individual rows can be set. The extra option can be specified
+following the same syntax as mode option, but following the entry.
+
+For example:
+
+```bash
+    echo -en "aap\0icon\x1ffolder\n"
+```
+
+The following options are supported:
+
+-   **icon**: Set the icon for that row.
+
+-   **display**: Replace the displayed string. (Original string will still be used for filtering)
+
+-   **meta**: Specify invisible search terms used for filtering.
+
+-   **nonselectable**: If true the row cannot activated.
+
+-   **permanent**: If true the row always shows, independent of filter.
+
+-   **info**: Info that, on selection, gets placed in the `ROFI_INFO`
+    environment variable. This entry does not get searched for filtering.
+
+-   **urgent**: Set urgent flag on entry (true/false)
+
+-   **active**: Set active flag on entry (true/false)
+
+multiple entries can be passed using the `\x1f` separator.
+
+```bash
+    echo -en "aap\0icon\x1ffolder\x1finfo\x1ftest\n"
+```
+
+## Executing external program
+
+If you want to launch an external program from the script, you need to make
+sure it is launched in the background. If not rofi will wait for its output (to
+display).
+
+In bash the best way to do this is using `coproc`.
+
+```bash
+ coproc ( myApp  > /dev/null  2>&1 )
+```
+
+## DASH shell
+
+If you use the `dash` shell for your script, take special care with how dash
+handles escaped values for the separators. See issue #1201 on github.
+
+## Script locations
+
+To specify a script there are the following options:
+
+- Specify an absolute path to the script.
+- The script is executable and located in your $PATH
+
+Scripts located in the following location are **loaded** on startup
+and can be directly launched based on the filename (without extension):
+
+- The script is in `$XDG_CONFIG_HOME/rofi/scripts/`, this is usually
+  `~/.config/rofi/scripts/`.
+
+If you have a script 'mymode.sh' in this folder you can open it using:
+
+```bash
+rofi -show mymode
+```
+
+See `rofi -h` output for a list of detected scripts.
+
+## SEE ALSO
+
+rofi(1), rofi-sensible-terminal(1), dmenu(1), rofi-theme(5),
+rofi-theme-selector(1)
+
+## AUTHOR
+
+Qball Cow <qball@gmpclient.org>
+
+Rasmus Steinke <rasi@xssn.at>
+
+Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: Sean Pringle <sean.pringle@gmail.com>
+
+For a full list of authors, check the AUTHORS file.
diff --git a/mkdocs/docs/1.7.7/rofi-sensible-terminal.1.markdown b/mkdocs/docs/1.7.7/rofi-sensible-terminal.1.markdown
new file mode 100644
index 000000000..1406299dd
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-sensible-terminal.1.markdown
@@ -0,0 +1,50 @@
+# rofi-sensible-terminal(1)
+
+## NAME
+
+**rofi-sensible-terminal** -  launches $TERMINAL with fallbacks
+
+## SYNOPSIS
+
+rofi-sensible-terminal [arguments]
+
+## DESCRIPTION
+
+rofi-sensible-terminal is invoked in the rofi default config to start a terminal. This
+wrapper script is necessary since there is no distribution-independent terminal launcher
+(but for example Debian has x-terminal-emulator). Distribution packagers are responsible for
+shipping this script in a way which is appropriate for the distribution.
+
+It tries to start one of the following (in that order):
+
+* `$TERMINAL` (this is a non-standard variable)
+* x-terminal-emulator
+* urxvt
+* rxvt
+* st
+* terminology
+* qterminal
+* Eterm
+* aterm
+* uxterm
+* xterm
+* roxterm
+* xfce4-terminal.wrapper
+* mate-terminal
+* lxterminal
+* konsole
+* alacritty
+* kitty
+* wezterm
+
+
+## SEE ALSO
+
+rofi(1)
+
+## AUTHORS
+
+Dave Davenport and contributors
+
+Copied script from i3:
+Michael Stapelberg and contributors
diff --git a/mkdocs/docs/1.7.7/rofi-theme-selector.1.markdown b/mkdocs/docs/1.7.7/rofi-theme-selector.1.markdown
new file mode 100644
index 000000000..1fa8b6fe7
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-theme-selector.1.markdown
@@ -0,0 +1,40 @@
+# rofi-theme-selector(1)
+
+## NAME
+
+**rofi-theme-selector** - Preview and apply themes for **rofi**
+
+## DESCRIPTION
+
+**rofi-theme-selector** is a bash/rofi script to preview and apply themes for
+**rofi**. It's part of any installation of **rofi**.
+
+## USAGE
+
+### Running rofi-theme-selector
+
+**rofi-theme-selector** shows a list of all available themes in a **rofi**
+window. It lets you preview each theme with the Enter key and apply the theme
+to your **rofi** configuration file with Alt+a.
+
+## Theme directories
+
+**rofi-theme-selector** searches the following directories for themes:
+
+- ${PREFIX}/share/rofi/themes
+- $XDG_CONFIG_HOME/rofi/themes
+- $XDG_DATA_HOME/share/rofi/themes
+
+${PREFIX} reflects the install location of rofi. In most cases this will be
+"/usr".<br>
+$XDG_CONFIG_HOME is normally unset. Default path is "$HOME/.config".<br>
+$XDG_DATA_HOME is normally unset. Default path is "$HOME/.local/share".
+
+## SEE ALSO
+
+rofi(1)
+
+## AUTHORS
+
+Qball Cow qball@gmpclient.org<br>
+Rasmus Steinke rasi@xssn.at
diff --git a/mkdocs/docs/1.7.7/rofi-theme.5.markdown b/mkdocs/docs/1.7.7/rofi-theme.5.markdown
new file mode 100644
index 000000000..dd6c2b4f1
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-theme.5.markdown
@@ -0,0 +1,1669 @@
+# rofi-theme(5)
+
+## NAME
+
+**rofi-theme** - Rofi theme format files
+
+## Getting started with theming
+
+The easiest way to get started theming rofi is by modifying your existing theme.
+
+Themes can be modified/tweaked by adding theming elements to the end of the\
+config file. The default location of this file is `~/.config/rofi/config.rasi`,
+if the file does not exists, you can create it.
+
+A basic config:
+
+```css
+configuration {
+  modes: [ combi ];
+  combi-modes: [ window, drun, run ];
+}
+
+@theme "gruvbox-light"
+ 
+/* Insert theme modifications after this */
+```
+
+For example if we want to change the `Type to filter` text in the entry box we
+append the following:
+
+```css
+entry {
+    placeholder: "Type here";
+}
+```
+
+In the above section, `entry` indicates the widget, `placeholder` is the
+property we want to modify and we set it to the string `"Type here"`. To find
+the commonly available widgets in rofi, see the 'Basic structure' section.
+
+To change the mouse over cursor to a pointer, add:
+
+```css
+entry {
+    placeholder: "Type here";
+    cursor: pointer;
+}
+```
+
+For the next modification, we want to add the icon after each text element and
+increase the size. First we start by modifying the `element` widget:
+
+```css
+
+element {
+  orientation: horizontal;
+  children: [ element-text, element-icon ];
+  spacing: 5px;
+}
+
+```
+
+Resulting in the following packing:
+
+```text
+┌─────────────────────────────────────────────────────────────────────┐ 
+│ element                                                             │ 
+│ ┌─────────────────────────────────────────────┐ ┌─────────────────┐ │ 
+│ │element─text                                 │ │ element─icon    │ │ 
+│ └─────────────────────────────────────────────┘ └─────────────────┘ │ 
+└─────────────────────────────────────────────────────────────────────┘ 
+```
+
+The `element` (container) widget hold each entry in the `listview`, we add the
+two pre-defined children in the order we want to show. We also specify the
+packing direction (`orientation`) and the spacing between the children
+(`spacing`). We specify the space between the two children in absolute pixels
+(`px`).
+
+To increase the icon-size, we need to modify the `element-icon` widget.
+
+```css
+element-icon {
+    size: 2.5em;
+}
+```
+
+```text
+┌─────────────────────────────────────────────────────────────────────┐ 
+│ element                                                             │ 
+│ ┌─────────────────────────────────────────────┐ ┌─────────────────┐ │ 
+│ │element─text                                 │ │    element      │ │ 
+│ │                                             │ │       ─         │ │ 
+│ │                                             │ │     icon        │ │ 
+│ └─────────────────────────────────────────────┘ └─────────────────┘ │ 
+└─────────────────────────────────────────────────────────────────────┘ 
+```
+
+In this example we specify the size in the [em](https://www.w3.org/Style/LieBos3e/em) unit.
+
+Now lets change the text color of both the `entry` and the `element-text`
+widget to red and background to blue.
+
+```css
+entry, element-text {
+  text-color: red;
+  background-color: rgb(0,0,255);
+}
+```
+
+Here we use two different methods of writing down the color, for `text-color`
+we used a named color, for `background-color` we specify it in `rgb`.
+We also specify the property for multiple widgets by passing a comma separated
+list of widget names.
+
+If you want to center the text relative to the icon, we can set this:
+
+```css
+element-text {
+    vertical-align: 0.5;
+}
+```
+
+```text
+┌─────────────────────────────────────────────────────────────────────┐ 
+│ element                                                             │ 
+│ ┌─────────────────────────────────────────────┐ ┌─────────────────┐ │ 
+│ │                                             │ │    element      │ │ 
+│ │element-text                                 │ │       ─         │ │ 
+│ │                                             │ │     icon        │ │ 
+│ └─────────────────────────────────────────────┘ └─────────────────┘ │ 
+└─────────────────────────────────────────────────────────────────────┘ 
+```
+
+We can also specify the color and width of the cursor. You could, for example,
+create a crimson block cursor like this:
+
+```css
+entry {
+  cursor-color: rgb(220,20,60);
+  cursor-width: 8px;
+}
+```
+
+By default, the `cursor-color` will be the same as the `text-color`. The
+`cursor-width` will always default to 2 pixels.
+
+If you want to see the complete theme, including the modification you can run:
+
+```bash
+rofi -dump-theme
+```
+
+## Default theme loading
+
+By default, rofi loads the default theme. This theme is **always** loaded.
+The default configuration contains:
+
+```css
+@theme "default"
+```
+
+To unload the default theme, and load another theme, add the `@theme` statement
+to your `config.rasi` file.
+
+If you have a theme loaded via `@theme` or use the default theme, you can tweak
+it by adding overriding elements at the end of your `config.rasi` file.
+
+For the difference between `@import` and `@theme` see the `Multiple file
+handling` section in this manpage.
+
+To see the default theme, run the following command:
+
+```bash
+rofi -no-config -dump-theme
+```
+
+## Description
+
+The need for a new theme format was motivated by the fact that the way rofi
+handled widgets has changed. From a very static drawing of lines and text to a
+nice structured form of packing widgets. This change made it possible to
+provide a more flexible theme framework. The old theme format and config file
+are not flexible enough to expose these options in a user-friendly way.
+Therefore, a new file format has been created, replacing the old one.
+
+## Format specification
+
+## Encoding
+
+The encoding of the file is UTF-8. Both unix (`\n`) and windows (`\r\n`)
+newlines format are supported. But unix is preferred.
+
+## Comments
+
+C and C++ file comments are supported.
+
+- Anything after  `//` and before a newline is considered a comment.
+
+- Everything between `/*` and `*/` is a comment, this comment can span
+    multiple lines.
+
+Comments can be nested and the C comments can be inline.
+
+The following is valid:
+
+```css
+// Magic comment.
+property: /* comment */ value;
+```
+
+However, this is not:
+
+```css
+prop/*comment*/erty: value;
+```
+
+## White space
+
+White space and newlines, like comments, are ignored by the parser.
+
+This:
+
+```css
+property: name;
+```
+
+Is identical to:
+
+```css
+     property             :
+name
+
+;
+```
+
+## File extension
+
+The preferred file extension for the new theme format is **rasi**. This is an
+abbreviation for **r**ofi **a**dvanced **s**tyle **i**nformation. If a theme
+file is split over multiple files, include files can have the: **rasinc**
+extension.
+
+## Basic Structure
+
+Each element has a section with defined properties. Global properties can be
+defined in section `* { }`. Sub-section names begin with an optional hash
+symbol `#`.
+
+It is advised to define the *global properties section* on top of the file to
+make inheritance of properties clearer.
+
+```css
+/* Global properties section */
+* {
+    // list of properties
+}
+
+/* Element theme section. */
+{element path} {
+    // list of properties
+}
+{elements... } {
+    // list of properties
+}
+```
+
+If there are multiple sections with the same name, they are merged. Duplicate
+properties are overwritten and the last parsed entry kept.
+
+## Global properties section
+
+A theme can have one or more global properties sections. If there is more than
+one, they will be merged.
+
+The global properties section denotes the defaults for each element.
+Each property of this section can be referenced with `@{identifier}`
+(See Properties section)
+
+A global properties section is indicated with a `*` as element path.
+
+## Element theme section
+
+A theme can have multiple element theme sections.
+
+The element path can consist of multiple names separated by whitespace or dots.
+Each element may contain any number of letters, numbers and `-`'s.
+The first element in the element path can optionally start with a `#` (for
+historic reasons). Multiple elements can be specified by a `,`.
+
+This is a valid element name:
+
+```css
+element normal.normal {
+    background-color: blue;
+}
+button {
+    background-color: blue;
+}
+```
+
+And is identical to:
+
+```css
+element normal normal, button {
+    background-color: blue;
+}
+```
+
+Each section inherits the global properties. Properties can be explicitly
+inherited from their parent with the `inherit` keyword.
+In the following example:
+
+```css
+window {
+ a: 1;
+ b: 2;
+ children: [ mainbox ];
+}
+mainbox {
+    a: inherit;
+    b: 4;
+    c: 8;
+}
+```
+
+The element `mainbox` will have the following set of properties (if `mainbox`
+is a child of `window`):
+
+```css
+a: 1;
+b: 4;
+c: 8;
+```
+
+If multiple sections are defined with the same name, they are merged by the
+parser. If multiple properties with the same name are defined in one section,
+the last encountered property is used.
+
+## Properties Format
+
+The properties in a section consist of:
+
+```css
+{identifier}: {value};
+```
+
+Both fields are mandatory for a property.
+
+The `identifier` names the specified property. Identifiers can consist of any
+combination of numbers, letters and '-'. It must not contain any whitespace.
+The structure of the `value` defines the type of the property. The current
+parser does not define or enforce a certain type of a particular `identifier`.
+When used, values with the wrong type that cannot be converted are ignored.
+
+The current theme format supports different types:
+
+- a string
+- an integer number
+- a fractional number
+- a boolean value
+- a color
+- image
+- text style
+- line style
+- a distance
+- a padding
+- a border
+- a position
+- a reference
+- an orientation
+- a cursor
+- a list of keywords
+- an array of values
+- an environment variable
+- Inherit
+
+Some of these types are a combination of other types.
+
+### String
+
+- Format:  `(["'])[:print:]+\1`
+
+Strings are always surrounded by double (`"`) or single (`'`, apostrophe) quotes. Between
+the quotes there can be any printable character.
+
+For example:
+
+```css
+font: "Awasome 12";
+```
+
+The string must be valid UTF-8, special characters can be escaped:
+
+```css
+text { content: "Line one\n\tIndented line two 'Quoted text'"; }
+text { content: 'Line one\n\tIndented line two "Quoted text"'; }
+text { content: "Line one\n\tIndented line two \"Quoted text\""; }
+```
+
+The following special characters can be escaped: `\b`, `\f`, `\n`, `\r`, `\t`, `\v`, `\`,
+`"` and `'` (double quotes inside single-quotes or in reverse don't need escape).
+
+### Integer
+
+- Format: `[-+]?[:digit:]+`
+
+An integer may contain any number.
+
+For examples:
+
+```css
+lines: 12;
+```
+
+### Real
+
+- Format: `[-+]?[:digit:]+(\.[:digit:]+)?`
+
+A real is an integer with an optional fraction.
+
+For example:
+
+```css
+real: 3.4;
+```
+
+The following is not valid: `.3`, `3.` or scientific notation: `3.4e-3`.
+
+### Boolean
+
+- Format: `(true|false)`
+
+Boolean value is either `true` or `false`. This is case-sensitive.
+
+For example:
+
+```css
+dynamic: false;
+```
+
+### Image
+
+**rofi** support a limited set of background-image formats.
+
+- Format: url("path to image");
+
+- Format: url("path to image", scale);
+    where scale is: none, both, width, height
+
+- Format: linear-gradient(stop color,stop1, color, stop2 color, ...);
+
+- Format: linear-gradient(to direction, stop color,stop1, color, stop2 color,
+    ...); where direction is:   top,left,right,bottom.
+
+- Format: linear-gradient(angle, stop color,stop1, color, stop2 color, ...);
+    Angle in deg,rad,grad (as used in color).
+
+Where the `path` is a string, and `stop` color is of type color.
+
+### Color
+
+**rofi** supports the color formats as specified in the CSS standard (1,2,3 and
+some of CSS 4)
+
+- Format: `#{HEX}{3}` (rgb)
+
+- Format: `#{HEX}{4}` (rgba)
+
+- Format: `#{HEX}{6}` (rrggbb)
+
+- Format: `#{HEX}{8}` (rrggbbaa)
+
+- Format: `rgb[a]({INTEGER},{INTEGER},{INTEGER}[, {PERCENTAGE}])`
+
+- Format: `rgb[a]({INTEGER}%,{INTEGER}%,{INTEGER}%[, {PERCENTAGE}])`
+
+- Format: `hsl[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
+
+- Format: `hwb[a]( {ANGLE}, {PERCENTAGE}, {PERCENTAGE} [, {PERCENTAGE}])`
+
+- Format: `cmyk( {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE}, {PERCENTAGE} [,
+    {PERCENTAGE} ])`
+
+- Format: `{named-color} [ / {PERCENTAGE} ]`
+
+The white-space format proposed in CSS4 is also supported.
+
+The different values are:
+
+- `{HEX}` is a hexadecimal number ('0-9a-f' case insensitive).
+
+- `{INTEGER}` value can be between 0 and 255 or 0-100 when representing
+    percentage.
+
+- `{ANGLE}` is the angle on the color wheel, can be in `deg`, `rad`, `grad`
+    or `turn`. When no unit is specified, degrees is assumed.
+
+- `{PERCENTAGE}` can be between 0-1.0, or 0%-100%
+
+- `{named-color}` is one of the following colors:
+
+    AliceBlue, AntiqueWhite, Aqua, Aquamarine, Azure, Beige, Bisque, Black,
+    BlanchedAlmond, Blue, BlueViolet, Brown, BurlyWood, CadetBlue, Chartreuse,
+    Chocolate, Coral, CornflowerBlue, Cornsilk, Crimson, Cyan, DarkBlue,
+    DarkCyan, DarkGoldenRod, DarkGray, DarkGrey, DarkGreen, DarkKhaki,
+    DarkMagenta, DarkOliveGreen, DarkOrange, DarkOrchid, DarkRed, DarkSalmon,
+    DarkSeaGreen, DarkSlateBlue, DarkSlateGray, DarkSlateGrey, DarkTurquoise,
+    DarkViolet, DeepPink, DeepSkyBlue, DimGray, DimGrey, DodgerBlue, FireBrick,
+    FloralWhite, ForestGreen, Fuchsia, Gainsboro, GhostWhite, Gold, GoldenRod,
+    Gray, Grey, Green, GreenYellow, HoneyDew, HotPink, IndianRed, Indigo,
+    Ivory, Khaki, Lavender, LavenderBlush, LawnGreen, LemonChiffon, LightBlue,
+    LightCoral, LightCyan, LightGoldenRodYellow, LightGray, LightGrey,
+    LightGreen, LightPink, LightSalmon, LightSeaGreen, LightSkyBlue,
+    LightSlateGray, LightSlateGrey, LightSteelBlue, LightYellow, Lime,
+    LimeGreen, Linen, Magenta, Maroon, MediumAquaMarine, MediumBlue,
+    MediumOrchid, MediumPurple, MediumSeaGreen, MediumSlateBlue,
+    MediumSpringGreen, MediumTurquoise, MediumVioletRed, MidnightBlue,
+    MintCream, MistyRose, Moccasin, NavajoWhite, Navy, OldLace, Olive,
+    OliveDrab, Orange, OrangeRed, Orchid, PaleGoldenRod, PaleGreen,
+    PaleTurquoise, PaleVioletRed, PapayaWhip, PeachPuff, Peru, Pink, Plum,
+    PowderBlue, Purple, RebeccaPurple, Red, RosyBrown, RoyalBlue, SaddleBrown,
+    Salmon, SandyBrown, SeaGreen, SeaShell, Sienna, Silver, SkyBlue, SlateBlue,
+    SlateGray, SlateGrey, Snow, SpringGreen, SteelBlue, Tan, Teal, Thistle,
+    Tomato, Turquoise, Violet, Wheat, White, WhiteSmoke, Yellow,
+    YellowGreen,transparent
+
+For example:
+
+```css
+background-color: #FF0000;
+border-color: rgba(0,0,1, 0.5);
+text-color: SeaGreen;
+```
+
+or
+
+```css
+background-color: transparent;
+text-color: Black;
+```
+
+### Text style
+
+- Format: `(bold|italic|underline|strikethrough|none)`
+
+Text style indicates how the highlighted text is emphasized. `None` indicates
+that no emphasis should be applied.
+
+- `bold`: make the text thicker then the surrounding text.
+- `italic`: put the highlighted text in script type (slanted).
+- `underline`: put a line under the text.
+- `strikethrough`: put a line through the text.
+
+The following options are available on pango 1.50.0 and up:
+
+- `uppercase`: Uppercase the text.
+- `lowercase`: Lowercase the text.
+
+The following option is disabled as pango crashes on this if there is eel
+upsizing or wrapping. This will be re-enabled once fixed:
+
+- `capitalize`: Capitalize the text.
+
+### Line style
+
+- Format: `(dash|solid)`
+
+Indicates how a line should be drawn.
+It currently supports:
+
+- `dash`:  a dashed line, where the gap is the same width as the dash
+- `solid`: a solid line
+
+### Distance
+
+- Format: `{Integer}px`
+- Format: `{Real}em`
+- Format: `{Real}ch`
+- Format: `{Real}%`
+- Format: `{Real}mm`
+
+A distance can be specified in 3 different units:
+
+- `px`: Screen pixels.
+- `em`: Relative to text height.
+- `ch`: Relative to width of a single number.
+- `mm`: Actual size in millimeters (based on dpi).
+- `%`:  Percentage of the **monitor** size.
+
+Distances used in the horizontal direction use the monitor width. Distances in
+the vertical direction use the monitor height.
+For example:
+
+```css
+   padding: 10%;
+```
+
+On a full-HD (1920x1080) monitor, it defines a padding of 192 pixels on the left
+and right side and 108 pixels on the top and bottom.
+
+#### Calculating sizes
+
+Rofi supports some maths in calculating sizes. For this it uses the CSS syntax:
+
+```css
+width: calc( 100% - 37px );
+```
+
+```css
+width: calc( 20% min 512 );
+```
+
+It supports the following operations:
+
+- `+`      : Add
+- `-`      : Subtract
+- `/`      : Divide
+- `-`      : Multiply
+- `modulo` : Modulo
+- `min`    : Minimum of lvalue or rvalue;
+- `max`    : Maximum of lvalue or rvalue;
+- `floor`  : Round down lvalue to the next multiple of rvalue
+- `ceil`   : Round up lvalue to the next multiple of rvalue
+- `round`  : Round lvalue to the next multiple of rvalue
+
+It uses the C precedence ordering.
+
+### Padding
+
+- Format: `{Integer}`
+- Format: `{Distance}`
+- Format: `{Distance} {Distance}`
+- Format: `{Distance} {Distance} {Distance}`
+- Format: `{Distance} {Distance} {Distance} {Distance}`
+
+If no unit is specified, pixels are assumed.
+
+The different number of fields in the formats are parsed like:
+
+- 1 field: `all`
+- 2 fields: `top&bottom` `left&right`
+- 3 fields: `top`, `left&right`, `bottom`
+- 4 fields: `top`, `right`, `bottom`, `left`
+
+### Border
+
+- Format: `{Integer}`
+
+- Format: `{Distance}`
+
+- Format: `{Distance} {Distance}`
+
+- Format: `{Distance} {Distance} {Distance}`
+
+- Format: `{Distance} {Distance} {Distance} {Distance}`
+
+- Format: `{Distance} {Line style}`
+
+- Format: `{Distance} {Line style} {Distance} {Line style}`
+
+- Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
+    style}`
+
+- Format: `{Distance} {Line style} {Distance} {Line style} {Distance} {Line
+    style} {Distance} {Line style}`
+
+Borders are identical to padding, except that each distance field has a line
+style property.
+
+> When no unit is specified, pixels are assumed.
+
+### Position
+
+Indicate a place on the window/monitor.
+
+```text
+┌─────────────┬─────────────┬─────────────┐
+│ north west  │    north    │  north east │
+├─────────────┼─────────────┼─────────────┤
+│   west      │   center    │     east    │
+├─────────────┼─────────────┼─────────────┤
+│ south west  │    south    │  south east │
+└─────────────┴─────────────┴─────────────┘
+```
+
+- Format: `(center|east|north|west|south|north east|north west|south west|south
+  east)`
+
+### Visibility
+
+It is possible to hide widgets:
+
+```css
+inputbar {
+    enabled: false;
+}
+```
+
+### Reference
+
+- Format: `@{PROPERTY NAME}`
+
+A reference can point to another reference. Currently, the maximum number of
+redirects is 20. A property always refers to another property. It cannot be
+used for a subpart of the property. For example, this is not valid:
+
+```css
+highlight: bold @pink;
+```
+
+But this is:
+
+```css
+* {
+    myhigh: bold #FAA;
+}
+
+window {
+    highlight: @myhigh;
+}
+```
+
+- Format: `var(PROPERTY NAME, DEFAULT)`
+
+A reference can point to another reference. Currently, the maximum number of
+redirects is 20. A property always refers to another property. It cannot be
+used for a subpart of the property.
+
+Example:
+
+```css
+window {
+    width: var( width, 30%);
+}
+```
+
+If the property `width` is set globally (`*{}`) that value is used, if the
+property `width` is not set, the default value is used.
+
+### Orientation
+
+- Format: `(horizontal|vertical)`
+
+Specify the orientation of the widget.
+
+### Cursor
+
+- Format: `(default|pointer|text)`
+
+Specify the type of mouse cursor that is set when the mouse pointer is over the
+widget.
+
+### List of keywords
+
+- Format: `[ keyword, keyword ]`
+
+A list starts with a '[' and ends with a ']'. The entries in the list are
+comma-separated. The `keyword` in the list refers to an widget name.
+
+### List of values
+
+- Format: `[ value, value, ... ]`
+
+An list starts with a '[' and ends with a ']'. The entries in the list are
+comma-separated.
+
+### Environment variable
+
+- Format: `${:alnum:}`
+
+This will parse the environment variable as the property value. (that then can
+be any of the above types). The environment variable should be an alphanumeric
+string without white-space.
+
+```css
+* {
+    background-color: ${BG};
+}
+```
+
+- Format: `env(ENVIRONMENT, default)`
+
+This will parse the environment variable as the property value. (that then can
+be any of the above types). The environment variable should be an alphanumeric
+string without white-space. If the environment value is not found, the default
+value is used.
+
+```css
+window {
+    width: env(WIDTH, 40%);
+}
+```
+
+If environment WIDTH is set, then that value is parsed, otherwise the default
+value (`40%`).
+
+### Inherit
+
+- Format: `inherit`
+
+Inherits the property from its parent widget.
+
+```css
+mainbox {
+    border-color: inherit;
+}
+```
+
+## Elements paths
+
+Element paths exists of two parts, the first part refers to the actual widget
+by name. Some widgets have an extra state.
+
+For example:
+
+```css
+element selected {
+}
+```
+
+Here `element selected` is the name of the widget, `selected` is the state of
+the widget.
+
+The difference between dots and spaces is purely cosmetic. These are all the
+same:
+
+```css
+element .selected {
+
+element.selected {
+}
+element selected {
+}
+```
+
+### Supported element paths
+
+### Base widgets
+
+The default widgets available in **rofi** and the default hierarchic:
+
+- `window`
+  - `overlay`: the overlay widget.
+
+  - `mainbox`: The mainbox box.
+
+  - `inputbar`: The input bar box.
+    - `box`: the horizontal @box packing the widgets
+
+    - `case-indicator`: the case/sort indicator @textbox
+
+    - `prompt`: the prompt @textbox
+
+    - `entry`: the main entry @textbox
+
+    - `num-rows`: Shows the total number of rows.
+
+    - `num-filtered-rows`: Shows the total number of rows after
+              filtering.
+
+    - `textbox-current-entry`: Shows the text of the currently selected
+              entry.
+
+    - `icon-current-entry`: Shows the icon of the currently selected
+              entry.
+
+  - `listview`: The listview.
+
+    - `scrollbar`: the listview scrollbar
+
+    - `element`: a box in the listview holding the entries
+
+      - `element-icon`: the widget in the listview's entry showing the
+   (optional) icon
+
+      - `element-index`: the widget in the listview's entry
+   keybindable index (1,2,3..0)
+
+      - `element-text`: the widget in the listview's entry showing the
+   text.
+
+  - `mode-switcher`: the main horizontal @box packing the buttons.
+    - `button`: the buttons @textbox for each mode
+
+  - `message`: The container holding the textbox.
+    - `textbox`: the message textbox
+
+Note that these path names match the default theme. Themes that provide a
+custom layout will have different elements, and structure.
+
+### State
+
+State: State of widget
+
+Optional flag(s) indicating state of the widget, used for theming.
+
+These are appended after the name or class of the widget.
+
+#### Example
+
+```
+button selected.normal { }
+
+element selected.urgent { }
+```
+
+Currently only the entrybox and scrollbar have states:
+
+#### Entrybox
+
+```
+{visible modifier}.{state}
+```
+
+Where `visible modifier` can be:
+
+- normal: no modification
+- selected: the entry is selected/highlighted by user
+- alternate: the entry is at an alternating row (uneven row)
+
+Where `state` is:
+
+- normal: no modification
+- urgent: this entry is marked urgent
+- active: this entry is marked active
+
+These can be mixed.
+
+Example:
+
+```css
+nametotextbox selected.active {
+    background-color: #003642;
+    text-color: #008ed4;
+}
+```
+
+Sets all selected textboxes marked active to the given text and background
+color. Note that a state modifies the original element, it therefore contains
+all the properties of that element.
+
+#### Scrollbar
+
+The scrollbar uses the `handle` state when drawing the small scrollbar handle.
+This allows the colors used for drawing the handle to be set independently.
+
+## Widget properties
+
+The following properties are currently supported:
+
+### all widgets
+
+- **enabled**:           enable/disable rendering of the widget
+
+- **padding**:           padding
+    Padding on the inside of the widget
+
+- **margin**:            padding
+    Margin on the outside of the widget
+
+- **border**:            border
+    Border around the widget (between padding and margin)/
+
+- **border-radius**:     padding
+    Sets a radius on the corners of the borders.
+
+- **background-color**:  color
+    Background color
+
+- **background-image**:  image
+    Background image
+
+- **border-color**:      color
+    Color of the border
+
+- **cursor**:            cursor
+    Type of mouse cursor that is set when the mouse pointer is hovered over the
+    widget.
+
+### window
+
+- **font**:            string
+    The font used in the window
+
+- **transparency**:    string
+    Indicating if transparency should be used and what type:
+  - **real** - True transparency. Only works with a compositor.
+  - **background** - Take a screenshot of the background image and use that.
+  - **screenshot** - Take a screenshot of the screen and use that.
+  - **Path** to png file - Use an image.
+
+- **location**:       position
+      The place of the anchor on the monitor
+
+- **anchor**:         anchor
+      The anchor position on the window
+
+- **fullscreen**:     boolean Window is fullscreen.
+
+- **width**:          distance The width of the window
+
+- **x-offset**:       distance
+
+- **y-offset**:       distance The offset of the window to the anchor point,
+    allowing you to push the window left/right/up/down
+
+### scrollbar Properties
+
+- **background-color**:    color
+- **handle-width**:        distance
+- **handle-color**:        color
+- **border-color**:        color
+
+### box
+
+- **orientation**:      orientation Set the direction the elements are packed.
+- **spacing**:          distance Distance between the packed elements.
+
+### textbox
+
+- **background-color**:  color
+
+- **border-color**:      the color used for the border around the widget.
+
+- **font**:              the font used by this textbox (string).
+
+- **str**/**content**:   the string to display by this textbox (string).
+
+- **vertical-align**:    Vertical alignment of the text. A number between 0
+    (top) and 1 (bottom).
+
+- **horizontal-align**:  Horizontal alignment of the text. A number between 0
+    (left) and 1 (right).
+
+- **text-color**:        the text color to use.
+
+- **text-transform**:    text style {color} for the whole text.
+
+- **highlight**:         text style {color}. color is optional, multiple
+    highlight styles can be added like: bold underline italic #000000; This
+    option is only available on the `element-text` widget.
+
+- **width**:             override the desired width for the textbox.
+
+- **content**:           Set the displayed text (String).
+
+- **placeholder**:       Set the displayed text (String) when nothing is
+    entered.
+
+- **placeholder-markup**:       If true, placeholder text supports pango
+    markup for stylizing.
+
+- **placeholder-color**: Color of the placeholder text.
+
+- **blink**:             Enable/Disable blinking on an input textbox
+    (Boolean).
+
+- **markup**:            Force markup on, beware that only valid pango markup
+    strings are shown.
+
+- **tab-stops**:         array of distances. Set the location of tab stops by
+    their distance from the beginning of the line. Each distance should be
+    greater than the previous one. The text appears to the right of the tab
+    stop position (other alignments are not supported yet).
+
+- **cursor-width**:      The width of the cursor.
+
+- **cursor-color**:      The color used to draw the cursor.
+
+- **cursor-outline**:      Enable a border (outline) around the cursor.
+    (Boolean)
+
+- **cursor-outline-width**: The width of the border around the cursor.
+    (Double)
+
+- **cursor-outline-color**: The color to use for the cursor outline.
+    (Color)
+
+- **text-outline**:      Enable a border (outline) around the text. (Boolean)
+
+- **text-outline-width**: The width of the border around the text.  (Double)
+
+- **text-outline-color**: The color to use for the text outline.    (Color)
+
+### listview
+
+- **columns**:         integer Number of columns to show (at least 1)
+
+- **fixed-height**:    boolean Always show `lines` rows, even if fewer
+    elements are available.
+
+- **dynamic**:         boolean `True` if the size should change when filtering
+    the list, `False` if it should keep the original height.
+
+- **scrollbar**:       boolean If the scrollbar should be enabled/disabled.
+
+- **scrollbar-width**: distance Width of the scrollbar
+
+- **cycle**:           boolean When navigating, it should wrap around
+
+- **spacing**:         distance Spacing between the elements (both vertical
+    and horizontal)
+
+- **lines**:           integer Number of rows to show in the list view.
+
+- **layout**:           orientation Indicate how elements are stacked.
+    Horizontal implements the dmenu style.
+
+- **reverse**:         boolean Reverse the ordering (top down to bottom up).
+
+- **flow**:           orientation The order the elements are layed out.
+    Vertical is the original 'column' view.
+
+- **fixed-columns**:    boolean Do not reduce the number of columns shown when
+    number of visible elements is not enough to fill them all.
+
+- **require-input**:    boolean Listview requires user input to be unhidden.
+    The list is still present and hitting accept will activate the first entry.
+
+## Listview widget
+
+The listview widget is special container widget.
+It has the following fixed children widgets:
+
+- 0 or more `element` widgets of the type box.
+
+- An optional `scrollbar` widget. This can be enabled using the scrollbar
+    property.
+
+These cannot be changed using the `children` property.
+
+Each Entry displayed by listview is captured by a `box` called `element`.
+An `element` widget can contain the following special child widgets:
+
+- `element-icon`: An icon widget showing the icon associated to the entry.
+- `element-text`: A textbox widget showing the text associated to the entry.
+- `element-index`: A textbox widget that shows the shortcut keybinding number.
+
+By default the `element-icon` and `element-text` child widgets are added to the
+`element`. This can be modified using the `children` property or the
+`[no]-show-icons` option.
+
+A child added with another name is treated the same as the special widget
+described in the [advanced layout](#advanced-layout) section.
+
+### listview text highlight
+
+The `element-text` widget in the `listview` is the one used to show the text.
+On this widget set the `highlight` property (only place this property is used)
+to change the style of highlighting. The `highlight` property consist of the
+`text-style` property and a color.
+
+To disable highlighting:
+
+```css
+  element-text {
+    highlight: None;
+  }
+```
+
+To set to red underlined:
+
+```css
+  element-text {
+    highlight: underline red;
+  }
+```
+
+## Layout
+
+The new format allows the layout of the **rofi** window to be tweaked
+extensively. For each widget, the themer can specify padding, margin, border,
+font, and more. It even allows, as an advanced feature, to pack widgets in a
+custom structure.
+
+### Basic layout structure
+
+The whole view is made out of boxes that pack other boxes or widgets.
+The box can be vertical or horizontal. This is loosely inspired by [GTK](http://gtk.org/).
+
+The current layout of **rofi** is structured as follows:
+
+```text
+┌────────────────────────────────────────────────────────────────────────────────────┐
+│ window {BOX:vertical}                                                              │
+│ ┌───────────────────────────────────────────────────────────────────────────────┐  │
+│ │ mainbox  {BOX:vertical}                                                       │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │ inputbar {BOX:horizontal}                                                 │ │  │
+│ │ │ ┌─────────┐ ┌─┐ ┌───────────────────────────────┐ ┌───┐ ┌───┐ ┌───┐ ┌───┐ │ │  │
+│ │ │ │ prompt  │ │:│ │ entry                         │ │#fr│ │ / │ │#ns│ │ci │ │ │  │
+│ │ │ └─────────┘ └─┘ └───────────────────────────────┘ └───┘ └───┘ └───┘ └───┘ │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ │                                                                               │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │ message                                                                   │ │  │
+│ │ │ ┌───────────────────────────────────────────────────────────────────────┐ │ │  │
+│ │ │ │ textbox                                                               │ │ │  │
+│ │ │ └───────────────────────────────────────────────────────────────────────┘ │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ │                                                                               │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │ listview                                                                  │ │  │
+│ │ │ ┌─────────────────────────────────────────────────────────────────────┐   │ │  │
+│ │ │ │ element                                                             │   │ │  │
+│ │ │ │ ┌─────────────────┐ ┌─────────────────────────────────────────────┐ │   │ │  │
+│ │ │ │ │element─icon     │ │element─text                                 │ │   │ │  │
+│ │ │ │ └─────────────────┘ └─────────────────────────────────────────────┘ │   │ │  │
+│ │ │ └─────────────────────────────────────────────────────────────────────┘   │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ │                                                                               │  │
+│ │ ┌───────────────────────────────────────────────────────────────────────────┐ │  │
+│ │ │  mode─switcher {BOX:horizontal}                                           │ │  │
+│ │ │ ┌───────────────┐   ┌───────────────┐  ┌──────────────┐ ┌───────────────┐ │ │  │
+│ │ │ │ Button        │   │ Button        │  │ Button       │ │ Button        │ │ │  │
+│ │ │ └───────────────┘   └───────────────┘  └──────────────┘ └───────────────┘ │ │  │
+│ │ └───────────────────────────────────────────────────────────────────────────┘ │  │
+│ └───────────────────────────────────────────────────────────────────────────────┘  │
+└────────────────────────────────────────────────────────────────────────────────────┘
+
+
+```
+>
+> - ci is the case-indicator
+> - fr is the num-filtered-rows
+> - ns is the num-rows
+
+### Error message structure
+
+```text
+┌──────────────────────────────────────────────────────────────────────────────────┐
+│ window {BOX:vertical}                                                            │
+│ ┌─────────────────────────────────────────────────────────────────────────────┐  │
+│ │ error─message {BOX:vertical}                                                │  │
+│ │ ┌────────────────────────────────────────────────────────────────────────┐  │  │
+│ │ │ textbox                                                                │  │  │
+│ │ └────────────────────────────────────────────────────────────────────────┘  │  │
+│ └─────────────────────────────────────────────────────────────────────────────┘  │
+└──────────────────────────────────────────────────────────────────────────────────┘
+
+```
+
+### Advanced layout
+
+The layout of **rofi** can be tweaked by packing the 'fixed' widgets in a
+custom structure.
+
+The following widgets are fixed, as they provide core **rofi** functionality:
+
+- prompt
+- entry
+- overlay
+- case-indicator
+- message
+- listview
+- mode-switcher
+- num-rows
+- num-filtered-rows
+
+The following keywords are defined and can be used to automatically pack a
+subset of the widgets. These are used in the default theme as depicted in the
+figure above.
+
+- mainbox Packs: `inputbar, message, listview, mode-switcher`
+- inputbar Packs: `prompt,entry,case-indicator`
+
+Any widget name starting with `textbox` is a textbox widget, others are box
+widgets and can pack other widgets.
+
+There are several special widgets that can be used by prefixing the name of the
+widget:
+
+#### Textbox widget
+
+This is a read-only textbox widget. The displayed string can be set with `content`.
+
+Example:
+
+```css
+textbox-custom {
+  expand: false;
+  content: "My Message";
+}
+```
+
+#### Icon
+
+This is an icon widget. The displayed icon can be set with `filename` and size
+with `size`. If the property `action` is set, it acts as a button. `action` can
+be set to a keybinding name and completes that action. (see rofi -show keys for
+a list).
+
+If the `squared` property is set to **false** the widget height and width are
+not forced to be equal.
+
+Example:
+
+```css
+icon-paste {
+    expand: false;
+    filename: "gtk-paste";
+    size: 24;
+    vertical-align: 0.5;
+    action: "kb-primary-paste";
+}
+```
+
+#### button
+
+This is a textbox widget that can have a 'clickable' action. The `action` can
+be set to: `keybinding`: accepts a keybinding name and completes that action.
+(see rofi -show keys for a list).
+
+```css
+button-paste {
+    expand: false;
+    content: "My Clickable Message";
+    vertical-align: 0.5;
+    action: "kb-primary-paste";
+}
+```
+
+#### Children
+
+To specify children, set the `children`
+property (this always happens on the `box` child, see example below):
+
+```css
+inputbar {
+  children: [prompt,entry,overlay,case-indicator];
+}
+```
+
+The theme needs to be updated to match the hierarchy specified.
+
+Below is an example of a theme emulating dmenu:
+
+```css
+* {
+    background-color:      Black;
+    text-color:            White;
+    border-color:          White;
+    font:            "Times New Roman 12";
+}
+
+window {
+    anchor:     north;
+    location:   north;
+    width:      100%;
+    padding:    4px;
+    children:   [ horibox ];
+}
+
+horibox {
+    orientation: horizontal;
+    children:   [ prompt, entry, listview ];
+}
+
+listview {
+    layout:     horizontal;
+    spacing:    5px;
+    lines:      10;
+}
+
+entry {
+    expand:     false;
+    width:      10em;
+}
+
+element {
+    padding: 0px 2px;
+}
+element selected {
+    background-color: SteelBlue;
+}
+```
+
+### Padding and margin
+
+Just like CSS, **rofi** uses the box model for each widget.
+
+```text
+┌──────────────────────────────────────────────────────────────────┐
+│ margin                                                           │
+│  ┌────────────────────────────────────────────────────────────┐  │
+│  │ border                                                     │  │
+│  │ ┌────────────────────────────────────────────────────────┐ │  │
+│  │ │ padding                                                │ │  │
+│  │ │ ┌────────────────────────────────────────────────────┐ │ │  │
+│  │ │ │ content                                            │ │ │  │
+│  │ │ └────────────────────────────────────────────────────┘ │ │  │
+│  │ └────────────────────────────────────────────────────────┘ │  │
+│  └────────────────────────────────────────────────────────────┘  │
+└──────────────────────────────────────────────────────────────────┘
+```
+
+Explanation of the different parts:
+
+- Content - The content of the widget.
+
+- Padding - Clears an area around the widget. The padding shows the
+    background color of the widget.
+
+- Border - A border that goes around the padding and content. The border use
+    the border-color of the widget.
+
+- Margin - Clears an area outside the border. The margin is transparent.
+
+The box model allows us to add a border around elements, and to define space
+between elements.
+
+The size of each margin, border, and padding can be set.
+For the border, a linestyle and radius can be set.
+
+### Spacing
+
+Widgets that can pack more then one child widget (currently box and listview)
+have the `spacing` property. This property sets the distance between the packed
+widgets (both horizontally and vertically).
+
+```text
+┌───────────────────────────────────────┐
+│ ┌────────┐ s ┌────────┐ s ┌────────┐  │
+│ │ child  │ p │ child  │ p │ child  │  │
+│ │        │ a │        │ a │        │  │
+│ │        │ c │        │ c │        │  │
+│ │        │ i │        │ i │        │  │
+│ │        │ n │        │ n │        │  │
+│ └────────┘ g └────────┘ g └────────┘  │
+└───────────────────────────────────────┘
+```
+
+### Advanced box packing
+
+More dynamic spacing can be achieved by adding dummy widgets, for example to
+make one widget centered:
+
+```text
+┌────────────────────────────────────────────────────┐
+│  ┌───────────────┐  ┌────────┐  ┌───────────────┐  │
+│  │ dummy         │  │ child  │  │ dummy         │  │
+│  │ expand: true; │  │        │  │ expand: true; │  │
+│  │               │  │        │  │               │  │
+│  │               │  │        │  │               │  │
+│  │               │  │        │  │               │  │
+│  └───────────────┘  └────────┘  └───────────────┘  │
+└────────────────────────────────────────────────────┘
+```
+
+If both dummy widgets are set to expand, `child` will be centered. Depending on
+the `expand` flag of child the remaining space will be equally divided between
+both dummy and child widget (expand enabled), or both dummy widgets (expand
+disabled).
+
+## Debugging
+
+To get debug information from the parser, run rofi like:
+
+```bash
+G_MESSAGES_DEBUG=Parser rofi -show run
+```
+
+Syntax errors are shown in a popup and printed out to command line with the
+above command.
+
+To see the elements queried during running, run:
+
+```bash
+G_MESSAGES_DEBUG=Theme rofi -show run
+```
+
+To test minor changes, part of the theme can be passed on the command line, for
+example to set it to full-screen:
+
+```bash
+rofi -theme-str 'window { fullscreen:true;}' -show run
+```
+
+Another syntax to modify theme properties is:
+
+```bash
+rofi -theme+window+fullscreen true -show run
+```
+
+To print the current theme, run:
+
+```bash
+rofi -dump-theme
+```
+
+## Media support
+
+Parts of the theme can be conditionally loaded, like the CSS `@media` option.
+
+```css
+@media ( min-width: 120 ) {
+
+}
+```
+
+It supports the following keys as constraint:
+
+- `min-width`:         load when width is bigger or equal then value.
+- `max-width`:         load when width is smaller then value.
+- `min-height`:        load when height is bigger or equal then value.
+- `max-height`:        load when height is smaller then value.
+- `min-aspect-ratio`   load when aspect ratio is over value.
+- `max-aspect-ratio`:  load when aspect ratio is under value.
+- `monitor-id`:        The monitor id, see rofi -help for id's.
+- `enabled`:           Boolean option to enable. Supports environment variable
+  or DMENU to detect if in dmenu mode.
+
+@media takes an integer number or a fraction, for integer number `px` can be
+added.
+
+```css
+@media ( min-width: 120 px ) {
+
+}
+```
+
+```css
+@media ( enabled: env(DO_LIGHT, false )) {
+
+}
+```
+
+```css
+@media ( enabled: DMENU) {
+
+}
+```
+
+## Conflicting constraints
+
+It is possible to define conflicting constraints in the theme. These conflicts
+are not explicitly reported. The most common example is forcing a specific
+window size, for example by enabling full-screen mode, having number of lines
+set in the listview and having the listview expand to available space. There is
+clearly a conflict in these 3 constraints. In this case, listview will not
+limit to the number of lines, but tries to fill the available space. It is up
+to the theme designer to make sure the theme handles this correctly.
+
+## Font Parsing
+
+Rofi uses [pango](https://pango.gnome.org/) for font rendering. The font should
+be specified in a format that pango understands. This normally is the font name
+followed by the font size. For example:
+
+```text
+mono 18
+```
+
+Or
+
+```text
+FontAwesome 22
+```
+
+From the pango manpage:
+
+The string must have the form
+
+```text
+\[FAMILY-LIST] \[STYLE-OPTIONS] \[SIZE] \[VARIATIONS]
+```
+
+where FAMILY-LIST is a comma-separated list of families optionally terminated
+by a comma, STYLE\_OPTIONS is a whitespace-separated list of words where each
+word describes one of style, variant, weight, stretch, or gravity, and SIZE is
+a decimal number (size in points) or optionally followed by the unit modifier
+“px” for absolute size. VARIATIONS is a comma-separated list of font variation
+specifications of the form “`axis`=value” (the = sign is optional).
+
+The following words are understood as styles: "Normal”, “Roman”, “Oblique”,
+“Italic”.
+
+The following words are understood as variants: “Small-Caps”, “All-Small-Caps”,
+“Petite-Caps”, “All-Petite-Caps”, “Unicase”, “Title-Caps”.
+
+The following words are understood as weights: “Thin”, “Ultra-Light”,
+“Extra-Light”, “Light”, “Semi-Light”, “Demi-Light”, “Book”, “Regular”,
+“Medium”, “Semi-Bold”, “Demi-Bold”, “Bold”, “Ultra-Bold”, “Extra-Bold”,
+“Heavy”, “Black”, “Ultra-Black”, “Extra-Black”.
+
+The following words are understood as stretch values: “Ultra-Condensed”,
+“Extra-Condensed”, “Condensed”, “Semi-Condensed”, “Semi-Expanded”, “Expanded”,
+“Extra-Expanded”, “Ultra-Expanded”.
+
+The following words are understood as gravity values: “Not-Rotated”, “South”,
+“Upside-Down”, “North”, “Rotated-Left”, “East”, “Rotated-Right”, “West”.
+
+Any one of the options may be absent. If FAMILY-LIST is absent, then the
+family\_name field of the resulting font description will be initialized to
+NULL. If STYLE-OPTIONS is missing, then all style options will be set to the
+default values. If SIZE is missing, the size in the resulting font description
+will be set to 0.
+
+A typical example:
+
+"Cantarell Italic Light 15 \`wght`=200"
+
+## Icon Handling
+
+Rofi supports 3 ways of specifying an icon:
+
+- Filename
+- icon-name, this is looked up via the icon-theme.
+- Markup String. It renders a string as an icon.
+
+For the first two options, GdkPixbuf is used to open and render the icons.
+This in general gives support for most required image formats.
+For the string option it uses Pango to render the string. The string needs to
+start with a `<span` tag, that allows you to set color and font.
+
+Markup string:
+
+```bash
+echo -en "testing\0icon\x1f<span color='red'>⏻</span>" | ./rofi -dmenu
+```
+
+Getting supported icon formats:
+
+```bash
+G_MESSAGES_DEBUG=Helpers.IconFetcher rofi
+```
+
+This uses the debug framework and prints out a list of supported image  file
+extensions.
+
+## Multiple file handling
+
+The rasi file format offers two methods of including other files. This can be
+used to modify existing themes, or have multiple variations on a theme.
+
+- import:  Import and parse a second file.
+- theme:   Discard theme, and load file as a fresh theme.
+
+Syntax:
+
+```css
+@import "myfile"
+@theme "mytheme"
+```
+
+The specified file can either by *name*, *filename*,*full path*.
+
+If a filename is provided, it will try to resolve it in the following order:
+
+- If path is absolute and file exists, it will open the file. This includes expansion of '~' or '~user'
+- On an `@import` or `@theme` it looks in the directory of the file that tried to include it.
+- `${XDG_CONFIG_HOME}/rofi/themes/`
+- `${XDG_CONFIG_HOME}/rofi/`
+- `${XDG_DATA_HOME}/rofi/themes/`
+- `${INSTALL PREFIX}/share/rofi/themes/`
+
+A name is resolved (if it has no valid extension) as a filename by appending the `.rasi` and the `.rasinc` extension.
+It will first look for files with `.rasi`, then for files with `.rasinc`.
+
+## Examples
+
+Several examples are installed together with **rofi**. These can be found in
+`{datadir}/rofi/themes/`, where `{datadir}` is the install path of **rofi**
+data. When installed using a package manager, this is usually: `/usr/share/`.
+
+## SEE ALSO
+
+rofi(1), rofi-script(5), rofi-theme-selector(1)
diff --git a/mkdocs/docs/1.7.7/rofi-thumbnails.5.markdown b/mkdocs/docs/1.7.7/rofi-thumbnails.5.markdown
new file mode 100644
index 000000000..e18ced7e1
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi-thumbnails.5.markdown
@@ -0,0 +1,85 @@
+# rofi-thumbnails(5)
+
+## NAME
+
+**rofi-thumbnails** - Rofi thumbnails system
+
+## DESCRIPTION
+
+**rofi** is now able to show thumbnails for all file types where an XDG compatible thumbnailer is present in the system.
+
+This is done by default in filebrowser and recursivebrowser mode, if **rofi** is launched with the `-show-icons` argument.
+
+In a custom user script or dmenu mode, it is possible to produce entry icons using XDG thumbnailers by adding the prefix `thumbnail://` to the filename
+specified after `\0icon\x1f`, for example:
+
+```bash
+echo -en "EntryName\0icon\x1fthumbnail://path/to/file\n" | rofi -dmenu -show-icons
+```
+
+### XDG thumbnailers
+
+XDG thumbnailers are files with a ".thumbnailer" suffix and a structure similar to ".desktop" files for launching applications. They are placed in `/usr/share/thumbnailers/` or `$HOME/.local/share/thumbnailers/`, and contain a list of mimetypes, for which is possible to produce the thumbnail image, and a string with the command to create said image. The example below shows the content of `librsvg.thumbnailer`, a thumbnailer for svg files using librsvg:
+
+```
+[Thumbnailer Entry]
+TryExec=/usr/bin/gdk-pixbuf-thumbnailer
+Exec=/usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
+MimeType=image/svg+xml;image/svg+xml-compressed;
+```
+
+The images produced are named as the md5sum of the input files and placed, depending on their size, in the XDG thumbnails directories: `$HOME/.cache/thumbnails/{normal,large,x-large,xx-large}`. They are then loaded by **rofi** as entry icons and can also be used by file managers like Thunar, Caja or KDE Dolphin to show their thumbnails. Additionally, if a thumbnail for a file is found in the thumbnails directories (produced previously by **rofi** or a file manager), **rofi** will load it instead of calling the thumbnailer.
+
+If a suitable thumbnailer for a given file is not found, **rofi** will try to use the corresponding mimetype icon from the icon theme. 
+
+### Custom command to create thumbnails
+
+It is possible to use a custom command to generate thumbnails for generic entry names, for example a script that downloads an icon given its url or selects different icons depending on the input. This can be done providing the `-preview-cmd` argument followed by a string with the command to execute, with the following syntax:
+
+```
+rofi ... -preview-cmd 'path/to/script_or_cmd "{input}" "{output}" "{size}"'
+```
+
+**rofi** will call the script or command substituting `{input}` with the input entry icon name (the string after `\0icon\x1fthumbnail://`), `{output}` with the output filename of the thumbnail and `{size}` with the requested thumbnail size. The script or command is responsible of producing a thumbnail image (if possible respecting the requested size) and saving it in the given `{output}` filename.
+
+### Issues with AppArmor
+
+In Linux distributions using AppArmor (such as Ubuntu and Debian), the default rules shipped can cause issues with thumbnails generation. If that is the case, AppArmor can be disabled by issuing the following commands
+
+```
+sudo systemctl stop apparmor
+sudo systemctl disable apparmor
+```
+
+In alternative, the following apparmor profile con be placed in a file named /etc/apparmor.d/usr.bin.rofi
+
+```
+#vim:syntax=apparmor
+# AppArmor policy for rofi
+
+#include <tunables/global>
+
+/usr/bin/rofi {
+    #include <abstractions/base>
+
+    # TCP/UDP network access for NFS
+    network inet  stream,
+    network inet6 stream,
+    network inet  dgram,
+    network inet6 dgram,
+
+    /usr/bin/rofi mr,
+
+    @{HOME}/ r,
+    @{HOME}/** rw,
+    owner @{HOME}/.cache/thumbnails/** rw,
+}
+```
+
+then run
+
+```
+apparmor_parser  -r /etc/apparmor.d/usr.bin.rofi
+```
+
+to reload the rule. This assumes that **rofi** binary is in /usr/bin, that is the case of a standard package installation.
diff --git a/mkdocs/docs/1.7.7/rofi.1.markdown b/mkdocs/docs/1.7.7/rofi.1.markdown
new file mode 100644
index 000000000..b740ea33f
--- /dev/null
+++ b/mkdocs/docs/1.7.7/rofi.1.markdown
@@ -0,0 +1,1186 @@
+# rofi(1)
+
+## NAME
+
+**rofi** - A window switcher, application launcher, ssh dialog, dmenu
+replacement and more
+
+## SYNOPSIS
+
+**rofi** [ -show *mode* ]|[ -dmenu ]|[ -e *msg* ] [ CONFIGURATION ]
+
+## DESCRIPTION
+
+**rofi** is an X11 pop-up window switcher, run dialog, dmenu replacement, and
+more. It focuses on being fast to use and have minimal distraction. It supports
+keyboard and mouse navigation, type to filter, tokenized search and more.
+
+## USAGE
+
+**rofi**'s main functionality is to assist in your workflow, allowing you to
+quickly switch between windows, start applications or log into a remote machine
+via `ssh`. There are different *modes* for different types of actions. **rofi**
+is a standalone application and should not be integrated into scripts. For
+integration into scripts it has a special mode that functions as a (drop-in)
+replacement for **dmenu(1)**. See emulating dmenu below.
+
+### Running rofi
+
+To launch **rofi** directly in a certain mode, specify a mode with `rofi -show
+<mode>`. To show the `drun` dialog:
+
+```bash
+    rofi -show drun
+```
+
+A useful setup in minimalistic window managers is to combine `drun`, `run`
+with `window` mode:
+
+```bash
+  rofi -show combi -modes combi -combi-modes "window,drun,run"
+```
+
+In this setup it first list all open applications, then all installed
+applications. So if you type firefox and hit return, it will switch to the
+running firefox, or launch it when it is not running.
+
+### Emulating dmenu
+
+**rofi** can emulate **dmenu(1)** (a dynamic menu for X11) when launched with
+the `-dmenu` flag.
+
+For more information see **rofi-dmenu(5)**.
+
+### Display Error message
+
+**rofi** error dialog can also be called from the command line.
+
+```bash
+    rofi -e "my message"
+```
+
+Markup support can be enabled, see CONFIGURATION options.
+
+## CONFIGURATION
+
+There are currently three methods of setting configuration options (evaluated
+in order below):
+
+- System configuration file  (for example `/etc/rofi.rasi`). It first checks
+    `XDG_CONFIG_DIRS`, and then `SYSCONFDIR` (that is passed at compile time).
+    It loads the first config file it finds, it does not merge multiple system
+    configuration files.
+
+- Rasi theme file: The new *theme* format can be used to set configuration
+    values.
+
+- Command-line options: Arguments passed to **rofi**.
+
+To get a template config file, run: `rofi -dump-config > config.rasi`
+
+This will contain (commented) all current configuration options, modified
+options are uncommented.
+
+To get a template config file that sets the icon-theme run: `rofi -icon-theme
+hicolor -dump-config`.
+
+It is **strongly** recommended to use this as a starting point for your
+configuration.
+
+An empty configuration section in the config file looks like:
+
+```css
+configuration {
+ // set config options here
+}
+```
+
+Most of the configuration options mentioned below (beside options like `-show`,
+`-dump-config` that apply to a single run) can be set here.
+
+For example to set the dpi value to 72:
+
+```css
+configuration {
+ dpi: 72;
+}
+```
+
+The configuration system supports the following types:
+
+- string
+- integer (signed and unsigned)
+- char
+- boolean
+- lists
+
+For the syntax of these options, see the **rofi-theme(5)** manpage.
+
+For use on the command line, Boolean options have a non-default command-line
+syntax. Example to enable option X:
+
+```text
+    -X
+```
+
+To disable option X:
+
+```text
+    -no-X
+```
+
+Below is a list of the most important options:
+
+### General
+
+`-help`
+
+The help option shows the full list of command-line options and the current set
+values. These include dynamic (run-time generated) options.
+
+`-version`
+
+Show the **rofi** version and exit.
+
+`-dump-config`
+
+Dump the current active configuration, in rasi format, to stdout and exit.
+Information about the rasi format can be found in the **rofi-theme(5)** manpage.
+
+`-dump-theme`
+
+Dump the current active theme, in rasi format, to stdout and exit.
+
+`-rasi-validate` *filename*
+
+Try to parse the file and return 0 when successful, non-zero when failed.
+
+`-list-keybindings`
+
+List all known keybindings without trying to parse them. This can be used to
+look for duplicate bindings.
+
+`-threads` *num*
+
+Specify the number of threads **rofi** should use:
+
+- 0: Autodetect the number of supported hardware threads.
+- 1: Disable threading
+- 2..n: Specify the maximum number of threads to use in the thread pool.
+
+Default:  Autodetect
+
+`-display` *display*
+
+The X server to contact. Default is `$DISPLAY`.
+
+`-dmenu`
+
+Run **rofi** in dmenu mode. This allows for interactive scripts.
+In `dmenu` mode, **rofi** reads from STDIN, and output to STDOUT.
+A simple example, displaying three pre-defined options:
+
+```bash
+    echo -e "Option #1\nOption #2\nOption #3" | rofi -dmenu
+```
+
+Or get the options from a script:
+
+```bash
+    ~/my_script.sh | rofi -dmenu
+```
+
+See the **rofi-dmenu(5)** manpage for more information.
+
+`-show` *mode*
+
+Open **rofi** in a certain mode. Available modes are `window`, `run`, `drun`,
+`ssh`, `combi`. The special argument `keys` can be used to open a searchable
+list of supported key bindings
+(see the **rofi-keys(5)** manpage)
+
+To show the run-dialog:
+
+```bash
+    rofi -show run
+```
+
+If `-show` is the last option passed to rofi, the first enabled modes is shown.
+
+`-modes` *mode1,mode2*
+
+Specify an ordered, comma-separated list of modes to enable.
+Enabled modes can be changed at runtime. Default key is `Ctrl+Tab`.
+If no modes are specified, all configured modes will be enabled.
+To only show the `run` and `ssh` launcher:
+
+```bash
+    rofi -modes "run,ssh" -show run
+```
+
+Custom modes can be added using the internal `script` mode. Each such mode has
+two parameters:
+
+```text
+<name>:<script>
+```
+
+Example: Have a mode called 'Workspaces' using the `i3_switch_workspaces.sh`
+script:
+
+```bash
+    rofi -modes "window,run,ssh,Workspaces:i3_switch_workspaces.sh" -show Workspaces
+```
+
+Notes: The i3 window manager dislikes commas in the command when specifying an
+exec command. For that case, `#` can be used as a separator.
+
+**TIP**: The name is allowed to contain spaces:
+
+```bash
+    rofi -modes "My File Browser:fb.sh" -show "My File Browser"
+```
+
+`-case-sensitive`
+
+Start in case-sensitive mode. This option can be changed at run-time using the
+`-kb-toggle-case-sensitivity` key binding.
+
+`-cycle`
+
+Cycle through the result list. Default is 'true'.
+
+`-filter` *filter*
+
+Filter the list by setting text in input bar to *filter*
+
+`-config` *filename*
+
+Load an alternative configuration file.
+
+`-cache-dir` *filename*
+
+Directory that is used to place temporary files, like history.
+
+`-scroll-method` *method*
+
+Select the scrolling method. 0: Per page, 1: continuous.
+
+`-normalize-match`
+
+Normalize the string before matching, so `o` will match `ö`, and `é` matches
+`e`.  This is not a perfect implementation, but works. For now, it disables
+highlighting of the matched part.
+
+`-no-lazy-grab`
+
+Disables lazy grab, this forces the keyboard being grabbed before gui is shown.
+
+`-no-plugins`
+
+Disable plugin loading.
+
+`-plugin-path` *directory*
+
+Specify the directory where **rofi** should look for plugins.
+
+`-show-icons`
+
+Show application icons in `drun` and `window` modes.
+
+`-icon-theme`
+
+Specify icon theme to be used. If not specified default theme from DE is used,
+*Adwaita* and *gnome* themes act as fallback themes.
+
+`-markup`
+
+Use Pango markup to format output wherever possible.
+
+`-normal-window`
+
+Make **rofi** react like a normal application window. Useful for scripts like
+Clerk that are basically an application.
+
+`-transient-window`
+
+Make **rofi** react like a modal dialog that is transient to the currently
+focused window. Useful when you use a keyboard shortcut to run and show
+on the window you are working with.
+
+`-[no-]steal-focus`
+
+Make rofi steal focus on launch and restore close to window that held it when
+launched.
+
+`-refilter-timeout-limit`
+
+The time (in ms) boundary filter may take before switch from instant to delayed
+filter mode.
+
+Default: 300
+
+A fallback icon can be specified for each mode:
+
+```css
+configuration {
+    <mode>{
+      fallback-icon: "<icon name>";
+    }
+}
+```
+
+Example
+
+```css
+configuration {
+    run,drun {
+      fallback-icon: "application-x-addon";
+    }
+}
+```
+
+### Matching
+
+`-matching` *method*
+
+Specify the matching algorithm used.
+Currently, the following methods are supported:
+
+- **normal**: match the int string
+- **regex**: match a regex input
+- **glob**: match a glob pattern
+- **fuzzy**: do a fuzzy match
+- **prefix**: match prefix
+
+Default: *normal*
+
+Note: glob matching might be slow for larger lists
+
+`-tokenize`
+
+Tokenize the input.
+
+`-drun-categories` *category1*,*category2*
+
+Only show desktop files that are present in the listed categories.
+
+`-drun-match-fields` *field1*,*field2*,...
+
+When using `drun`, match only with the specified Desktop entry fields.
+The different fields are:
+
+- **name**: the application's name
+- **generic**: the application's generic name
+- **exec**: the application's  executable
+- **categories**: the application's categories
+- **comment**: the application comment
+- **all**: all the above
+
+Default: *name,generic,exec,categories,keywords*
+
+`-drun-display-format`
+
+The format string for the `drun` dialog:
+
+- **name**: the application's name
+- **generic**: the application's generic name
+- **exec**: the application's  executable
+- **categories**: the application's categories
+- **comment**: the application comment
+- **url**: The url in case of a link type desktop file
+
+Pango markup can be used to formatting the output.
+
+Default: `{name} [<span weight='light' size='small'><i>({generic})</i></span>]`
+
+Note: Only fields enabled in `-drun-match-fields` can be used in the format
+string.
+
+`-[no-]drun-show-actions`
+
+Show actions present in the Desktop files.
+
+Default: false
+
+`-window-match-fields` *field1*,*field2*,...
+
+When using window mode, match only with the specified fields.
+The different fields are:
+
+- **title**: window's title
+- **class**: window's class
+- **role**: window's role
+- **name**: window's name
+- **desktop**: window's current desktop
+- **all**: all the above
+
+Default: *all*
+
+`-matching-negate-char` *string*
+
+Set the character used to negate the query (i.e. if it does **not** match the
+next keyword). Set to '\x0' to disable. It takes the first ASCII character from the string.
+
+Default: '-'
+
+### Filtered menu sort
+
+`-[no]-sort`
+
+Enable, disable sort for filtered menu.
+This setting can be changed at runtime (see `-kb-toggle-sort`).
+
+`-sorting-method` 'method' to specify the sort method.
+
+There are 2 methods:
+
+- **levenshtein** (Default)
+- **fzf**
+
+### Layout and Theming
+
+**IMPORTANT:** In newer **rofi** releases, all the theming options have been
+moved into the new theme format. They are no longer normal **rofi** options
+that can be passed directly on the command line (there are too many). Small
+snippets can be passed on the command line: `rofi -theme-str 'window {width:
+50%;}'` to override a single setting. They are merged into the current theme.
+They can also be appended at the end of the **rofi** config file to override
+parts of the theme.
+
+Most of the following options are **deprecated** and should not be used. Please
+use the new theme format to customize **rofi**. More information about the new
+format can be found in the **rofi-theme(5)** manpage.
+
+`-location`
+
+Specify where the window should be located. The numbers map to the following
+locations on screen:
+
+```text
+      1 2 3
+      8 0 4
+      7 6 5
+```
+
+Default: *0*
+
+`-fixed-num-lines`
+
+Keep a fixed number of visible lines.
+
+`-sidebar-mode`
+
+Open in sidebar-mode. In this mode, a list of all enabled modes is shown at the
+bottom (See `-modes` option). To show sidebar, use:
+
+```bash
+    rofi -show run -sidebar-mode 
+```
+
+`-hover-select`
+
+Automatically select the entry the mouse is hovering over. This option is best
+combined with custom mouse bindings. To utilize hover-select and accept an
+entry in a single click, use:
+
+```bash
+    rofi -show run -hover-select -me-select-entry '' -me-accept-entry MousePrimary
+```
+
+`-eh` *number*
+
+Set row height (in chars)
+Default: *1*
+
+`-auto-select`
+
+When one entry is left, automatically select it.
+
+`-m` *num*,  `-m` *name*, `-monitor` *num*, `-monitor` *name*
+
+Select monitor to display **rofi** on. It accepts as input: *primary* (if
+primary output is set), the *xrandr* output name, or integer number (in order
+of detection). Negative numbers are handled differently:
+
+- **-1**: the currently focused monitor.
+
+- **-2**: the currently focused window (that is, **rofi** will be displayed
+    on top of the focused window).
+
+- **-3**: Position of mouse (overrides the location setting to get normal
+    context menu behavior.)
+
+- **-4**: the monitor with the focused window.
+
+- **-5**: the monitor that shows the mouse pointer.
+
+Default: *-5*
+
+See `rofi -h` output for the detected monitors, their position, and size.
+
+`-theme` *filename*
+
+Path to the new theme file format. This overrides the old theme settings.
+
+`-theme-str` *string*
+
+Allow theme parts to be specified on the command line as an override.
+
+For example:
+
+```bash
+    rofi -theme-str '#window { fullscreen: true; }'
+```
+
+This option can be specified multiple times.
+This is now the method to tweak the theme via the command line.
+
+`-dpi`  *number*
+
+Override the default DPI setting.
+
+- If set to `0`, it tries to auto-detect based on X11 screen size (similar to
+    i3 and GTK).
+
+- If set to `1`, it tries to auto-detect based on the size of the monitor
+    that **rofi** is displayed on (similar to latest Qt 5).
+
+`-selected-row` *selected row*
+
+Select a certain row.
+
+Default: *0*
+
+### PATTERN setting
+
+`-terminal`
+
+Specify which terminal to start.
+
+```bash
+    rofi -terminal xterm
+```
+
+Pattern: *{terminal}*
+
+Default: *x-terminal-emulator*
+
+`-ssh-client` *client*
+
+Override the used `ssh` client.
+
+Pattern: *{ssh-client}*
+
+Default: *ssh*
+
+### SSH settings
+
+`-ssh-command` *cmd*
+
+Set the command to execute when starting an ssh session.
+The pattern *{host}* is replaced by the selected ssh entry.
+
+Pattern: *{ssh-client}*
+
+Default: *{terminal} -e {ssh-client} {host}*
+
+`-parse-hosts`
+
+Parse the `/etc/hosts` file for entries.
+
+Default: *disabled*
+
+`-[no-]parse-known-hosts`
+
+Parse the `~/.ssh/known_hosts` file for entries.
+
+Default: *enabled*
+
+### Run settings
+
+`-run-command` *cmd*
+
+Set command (*{cmd}*) to execute when running an application.
+See *PATTERN*.
+
+Default: *{cmd}*
+
+Example to run applications in a dedicated cgroup with systemd. Requires a
+shell to escape and interpolate the unit name correctly.
+
+```bash
+"bash -c 'systemd-run --user --unit=app-rofi-\$(systemd-escape {cmd})-\$RANDOM {cmd}'"
+```
+
+`-run-shell-command` *cmd*
+
+Set command to execute when running an application in a shell.
+See *PATTERN*.
+
+Default: *{terminal} -e {cmd}*
+
+`-run-list-command` *cmd*
+
+If set, use an external tool to generate a list of executable commands. Uses
+`run-command`.
+
+Default: *{cmd}*
+
+### Window switcher settings
+
+`-window-format` *format*
+
+Format what is being displayed for windows.
+
+*format*: {field[:len]}
+
+*field*:
+
+- **w**: desktop name
+- **t**: title of window
+- **n**: name
+- **r**: role
+- **c**: class
+
+*len*: maximum field length (0 for auto-size). If length is negative, the entry
+will be unchanged. If length is positive, the entry will be truncated or padded
+to fill that length.
+
+default: {w}  {c}   {t}
+
+`-window-command` *cmd*
+
+Set command to execute on selected window for an alt action (`-kb-accept-alt`).
+See *PATTERN*.
+
+Default: *"wmctrl -i -R {window}"*
+
+`-window-thumbnail`
+
+Show window thumbnail (if available) as icon in the window switcher.
+
+You can stop rofi from exiting when closing a window (allowing multiple to be
+closed in a row).
+
+```css
+configuration {
+  window {
+      close-on-delete: false;
+  }
+}
+```
+
+You can hide the currently active window with the 'hide-active-window' setting:
+
+```css
+configuration {
+  window {
+      hide-active-window: true;
+  }
+}
+```
+
+or pass `-window-hide-active-window true` on command line.
+
+You can prefer the icon theme above the window set icon with the
+'prefer-icon-theme' setting:
+
+```css
+configuration {
+  window {
+      prefer-icon-theme: true;
+  }
+}
+```
+
+or pass `-window-prefer-icon-theme true` on command line.
+
+### Combi settings
+
+`-combi-modes` *mode1*,*mode2*
+
+The modes to combine in combi mode.
+For syntax to `-combi-modes`, see `-modes`.
+To get one merge view, of `window`,`run`, and `ssh`:
+
+```bash
+    rofi -show combi -combi-modes "window,run,ssh" -modes combi
+```
+
+**NOTE**: The i3 window manager dislikes commas in the command when specifying
+an exec command. For that case, `#` can be used as a separator.
+
+`-combi-display-format`
+
+The format string for entries in the `combi` dialog:
+
+- **mode**: the mode display name
+- **text**: the entry text
+
+Pango markup can be used to formatting the output.
+
+Default: {mode} {text}
+
+Note: This setting is ignored if `combi-hide-mode-prefix` is enabled.
+
+### History
+
+`-[no-]disable-history`
+
+Disable or re-enable history
+
+`-max-history-size` *number*
+
+Maximum number of entries to store in history. Defaults to 25. (WARNING: can
+cause slowdowns when set too high)
+
+### Message dialog
+
+`-e` *message*
+
+Pops up a message dialog (used internally for showing errors) with *message*.
+Message can be multi-line.
+
+Passing `-e -` reads (blocking) from standard in and displays this.
+
+### File browser settings
+
+File browser behavior can be controlled via the following options:
+
+```css
+configuration {
+   filebrowser {
+      /** Directory the file browser starts in. */
+      directory: "/some/directory";
+      /**
+        * Sorting method. Can be set to:
+        *   - "name"
+        *   - "mtime" (modification time)
+        *   - "atime" (access time)
+        *   - "ctime" (change time)
+        */
+      sorting-method: "name";
+      /** Group directories before files. */
+      directories-first: true;
+      /** Show hidden files. */
+      show-hidden: false;
+      /** return 1 on cancel. */
+      cancel-returns-1: true;
+      /** command */
+      command: "xdg-open";
+   }
+}
+```
+
+These options can also be passed on the commandline, for example:
+
+```bash
+rofi -filebrowser-cancel-returns-1 true -show filebrowser
+```
+
+The `show-hidden` can also be triggered with the `kb-delete-entry` keybinding.
+
+### Recursive Browser settings
+
+Recursive file browser behavior can be controlled via the following options:
+
+```css
+configuration {
+   recursivebrowser {
+      /** Directory the file browser starts in. */
+      directory: "/some/directory";
+      /** return 1 on cancel. */
+      cancel-returns-1: true;
+      /** filter entries using regex */
+      filter-regex: "(.*cache.*|.*\.o)";
+      /** command */
+      command: "xdg-open";
+   }
+}
+```
+
+### Entry history
+
+The number of previous inputs for the entry box can be modified by setting
+max-history on the entry box.
+
+```css
+configuration {
+    entry  {
+        max-history: 30;
+    }
+}
+```
+
+By default the file is stored in the systems cache directory, in a file called
+`rofi-entry-history.txt`.
+
+### Other
+
+`-drun-use-desktop-cache`
+
+Build and use a cache with the content of desktop files. Usable for systems
+with slow hard drives.
+
+`-drun-reload-desktop-cache`
+
+If `drun-use-desktop-cache` is enabled, rebuild a cache with the content of
+desktop files.
+
+`-drun-url-launcher` *command*
+
+Command to open a Desktop Entry that is a Link.
+
+`-pid` *path*
+
+Make **rofi** create a pid file and check this on startup. The pid file
+prevents multiple **rofi** instances from running simultaneously. This is
+useful when running **rofi** from a key-binding daemon.
+
+`-replace`
+
+If rofi is already running, based on pid file, try to kill that instance.
+
+`-display-{mode}` *string*
+
+Set the name to use for mode. This is used as prompt and in combi-browser.
+
+It is now preferred to use the configuration file:
+
+```css
+configuration {
+  {mode} {
+    display-name: *string*;
+  }
+}
+```
+
+`-[no-]click-to-exit`
+
+Click the mouse outside the **rofi** window to exit.
+
+Default: *enabled*
+
+`-xserver-i300-workaround`
+
+Workaround for bug in Xserver. See issue #611 and #1642 on the rofi issue
+tracker.
+
+Default: *disabled*
+
+## PATTERN
+
+To launch commands (for example, when using the ssh launcher), the user can
+enter the used command-line. The following keys can be used that will be
+replaced at runtime:
+
+- `{host}`: the host to connect to
+- `{terminal}`: the configured terminal (see -terminal)
+- `{ssh-client}`: the configured ssh client (see -ssh-client)
+- `{cmd}`: the command to execute
+- `{window}`: the window ID of the selected window (in `window-command`)
+
+It processes the string as follows: `{key}`
+is replaced by its value, if `{key}` is not set it is removed. If the `{key}`
+is in between `[]`  all the text between `[]` is removed if `{key}` is not set.
+Otherwise key is replaced and the `[]` are removed.
+
+For example: `{ssh-client} [-p {port}] {host}`
+
+## THEMING
+
+Please see **rofi-theme(5)** manpage for more information on theming.
+
+## KEY BINDINGS
+
+Please see the **rofi-keys(5)** manpage for the keybindings and how to set them
+up.
+
+The keybinding can also be used for actions, when the action is executed the
+mentioned keystroke is inserted:
+
+### Timeout
+
+You can configure an action to be taken when rofi has not been interacted
+with for a certain amount of seconds. You can specify a keybinding to trigger
+after X seconds.
+
+```css
+configuration {
+  timeout {
+      delay:  15;
+      action: "kb-cancel";
+  }
+}
+```
+
+### Input change
+
+When the input of the textbox changes:
+
+```css
+configuration {
+  inputchange {
+      action: "kb-row-first";
+  }
+}
+```
+
+## Available Modes
+
+### window
+
+Show a list of all the windows and allow switching between them. Pressing the
+`delete-entry` binding (`shift-delete`) will close the window. Pressing the
+`accept-custom` binding (`control-enter` or `shift-enter`) will run a command
+on the window. (See option `window-command` );
+
+If there is no match, it will try to launch the input.
+
+### windowcd
+
+Shows a list of the windows on the current desktop and allows switching between
+them. Pressing the `delete-entry` binding (`shift-delete`) will kill the
+window. Pressing the `accept-custom` binding (`control-enter` or `shift-enter`)
+will run a command on the window. (See option `window-command` );
+
+If there is no match, it will try to launch the input.
+
+### run
+
+Shows a list of executables in `$PATH` and can launch them (optional in a
+terminal).
+
+- Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
+    from the run history.
+
+- Pressing the `accept-custom` binding (`control-enter`) will run the command
+    as entered in the entry box.
+
+- Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
+    terminal.
+
+When pressing the `mode-complete` binding (`Control-l`), you can use the File
+Browser mode to launch the application with a file as the first argument.
+
+### drun
+
+Same as the **run** launches, but the list is created from the installed
+desktop files. It automatically launches them in a terminal if specified in the
+Desktop File.
+
+- Pressing the `delete-entry` binding (`shift-delete`) will remove this entry
+    from the run history.
+
+- Pressing the `accept-custom` binding (`control-enter`) will run the command
+    as entered in the entry box.
+
+- Pressing the `accept-alt` binding (`shift-enter`) will run the command in a
+    terminal.
+
+When pressing the `mode-complete` binding (`Control-l`), you can use the File
+Browser mode to launch the application passing a file as argument if specified
+in the desktop file.
+
+The DRUN mode tries to follow the [XDG Desktop Entry
+Specification](https://freedesktop.org/wiki/Specifications/desktop-entry-spec/)
+and should be compatible with applications using this standard.  Some
+applications create invalid desktop files, **rofi** will discard these entries.
+See the debugging section for more info on DRUN mode, this will print why
+desktop files are discarded.
+
+There are a few advanced options to tweak the behaviour:
+
+```css
+configuration {
+   drun {
+      /** Scan the current users desktop for desktop files. */
+      scan-desktop: true;
+      /** Parse user desktop files. */
+      parse-user:   true;
+      /** Parse system desktop files. */
+      parse-system: false;
+   }
+}
+```
+
+### ssh
+
+Shows a list of SSH targets based on your `ssh` config file, and allows to
+quickly `ssh` into them.
+
+### keys
+
+Shows a searchable list of key bindings.
+
+### script
+
+Allows custom scripted Modes to be added, see the **rofi-script(5)** manpage
+for more information.
+
+### combi
+
+Combines multiple modes in one list. Specify which modes are included with the
+`-combi-modes` option.
+
+When using the combi mode, a *!bang* can be used to filter the results by modes.
+All modes that match the bang as a prefix are included.
+For example, say you have specified `-combi-modes run,window,windowcd`. If your
+query begins with the bang `!w`, only results from the `window` and `windowcd`
+modes are shown, even if the rest of the input text would match results from `run`.
+
+If no match, the input is handled by the first combined modes.
+
+## FAQ
+
+### The text in the window switcher is not nicely aligned
+
+Try using a mono-space font or tabs + the tab-stops setting..
+
+### The window is completely black
+
+Check quotes used on the command-line: you might have used `“` ("smart quotes")
+instead of `"` ("machine quotes").
+
+### What does the icon in the top right show?
+
+The indicator shows:
+
+- `` Case insensitive and no sorting.
+- `-` Case sensitivity enabled, no sorting.
+- `+` Case insensitive and Sorting enabled
+- `±` Sorting and Case sensitivity enabled"
+
+### Why do I see different icons for run,drun and window mode
+
+Each of these modes uses different methods of resolving the icon:
+
+- Window: It first uses the icon that the application exposes via the X11
+    Server, if none is set it does a lookup of the window Class name in the icon
+    theme.
+
+- drun: It uses the icon set in the desktop file.
+
+- run: It does a lookup using the executable name.
+
+## EXAMPLES
+
+Some basic usage examples of **rofi**:
+
+Show the run dialog:
+
+```bash
+    rofi -modes run -show run
+```
+
+Show the run dialog, and allow switching to Desktop File run dialog (`drun`):
+
+```bash
+    rofi -modes run,drun -show run
+```
+
+Combine the run and Desktop File run dialog (`drun`):
+
+```bash
+    rofi -modes combi -show combi -combi-modes run,drun
+```
+
+Combine the run and Desktop File run dialog (`drun`), and allow switching to
+window switcher:
+
+```bash
+    rofi -modes combi,window -show combi -combi-modes run,drun
+```
+
+Pop up a text message claiming that this is the end:
+
+```bash
+    rofi -e "This is the end"
+```
+
+Pop up a text message in red, bold font claiming that this is still the end:
+
+```bash
+    rofi -e "<span color='red'><b>This is still the end</b></span>" -markup
+```
+
+Show all key bindings:
+
+```bash
+    rofi -show keys
+```
+
+## i3
+
+In [i3](http://i3wm.org/) you want to bind **rofi** to be launched on key
+release. Otherwise, it cannot grab the keyboard. See also the i3
+[manual](http://i3wm.org/docs/userguide.html):
+
+Some tools (such as `import` or `xdotool`) might be unable to run upon a
+KeyPress event, because the keyboard/pointer is still grabbed. For these
+situations, the `--release` flag can be used, as it will execute the command
+after the keys have been released.
+
+## LICENSE
+
+```text
+    MIT/X11
+
+    Permission is hereby granted, free of charge, to any person obtaining
+    a copy of this software and associated documentation files (the
+    "Software"), to deal in the Software without restriction, including
+    without limitation the rights to use, copy, modify, merge, publish,
+    distribute, sublicense, and/or sell copies of the Software, and to
+    permit persons to whom the Software is furnished to do so, subject to
+    the following conditions:
+
+    The above copyright notice and this permission notice shall be
+    included in all copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+    OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+    MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+    IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+    CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+    TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+    SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+```
+
+## WEBSITE
+
+**rofi** website can be found [here](https://github.com/davatorium/rofi/)
+
+## SUPPORT
+
+**rofi** support can be obtained:
+
+- [GitHub Discussions](https://github.com/davatorium/rofi/discussions)
+- [IRC](irc://irc.libera.chat:6697/#rofi) (#rofi on irc.libera.chat),
+
+## DEBUGGING
+
+For more information see **rofi-debugging(5)** manpage.
+
+## ISSUE TRACKER
+
+The **rofi** issue tracker can be found [here](https://github.com/davatorium/rofi/issues)
+Before creating an issue, consider posting a question on the [discussion forum](https://github.com/davatorium/rofi/discussions) first.
+When creating an issue, please read [this](https://github.com/davatorium/rofi/blob/master/.github/CONTRIBUTING.md)
+first.
+
+## SEE ALSO
+
+**rofi-sensible-terminal(1)**, **dmenu(1)**, **rofi-debugging(5)**,
+**rofi-theme(5)**, **rofi-script(5)**,
+**rofi-keys(5)**,**rofi-theme-selector(1)**,**rofi-dmenu(5)**
+
+## AUTHOR
+
+- Qball Cow <qball@blame.services>
+- Rasmus Steinke <rasi@xssn.at>
+- Morgane Glidic <sardemff7+rofi@sardemff7.net>
+
+Original code based on work by: [Sean Pringle](https://github.com/seanpringle/simpleswitcher) <sean.pringle@gmail.com>
+
+For a full list of authors, check the `AUTHORS` file.
diff --git a/mkdocs/docs/current/rofi-thumbnails.5.markdown b/mkdocs/docs/current/rofi-thumbnails.5.markdown
new file mode 120000
index 000000000..165107534
--- /dev/null
+++ b/mkdocs/docs/current/rofi-thumbnails.5.markdown
@@ -0,0 +1 @@
+../../../doc/rofi-thumbnails.5.markdown
\ No newline at end of file
diff --git a/mkdocs/docs/downloads.md b/mkdocs/docs/downloads.md
index 77febdae5..35f75bc85 100644
--- a/mkdocs/docs/downloads.md
+++ b/mkdocs/docs/downloads.md
@@ -6,6 +6,11 @@ For development no tarball is released. Please follow the
 [Installation](../INSTALL/) instructions for obtaining and compiling
 development version.
 
+## [1.7.6](https://github.com/davatorium/rofi/releases/tag/1.7.6)
+
+- [tar.gz](https://github.com/davatorium/rofi/releases/download/1.7.6/rofi-1.7.6.tar.gz)
+- [tar.xz](https://github.com/davatorium/rofi/releases/download/1.7.6/rofi-1.7.6.tar.xz)
+
 ## [1.7.5](https://github.com/davatorium/rofi/releases/tag/1.7.5)
 
 - [tar.gz](https://github.com/davatorium/rofi/releases/download/1.7.5/rofi-1.7.5.tar.gz)
diff --git a/mkdocs/mkdocs.yml b/mkdocs/mkdocs.yml
index 4dfa71485..7ebe364e2 100644
--- a/mkdocs/mkdocs.yml
+++ b/mkdocs/mkdocs.yml
@@ -22,6 +22,23 @@ nav:
     - Script: current/rofi-script.5.markdown
     - Debugging: current/rofi-debugging.5.markdown
     - Keys: current/rofi-keys.5.markdown
+    - Thumbnails: current/rofi-thumbnails.5.markdown
+  - 1.7.7:
+    - Rofi: 1.7.7/rofi.1.markdown 
+    - Themes: 1.7.7/rofi-theme.5.markdown
+    - Dmenu: 1.7.7/rofi-dmenu.5.markdown
+    - Script: 1.7.7/rofi-script.5.markdown
+    - Debugging: 1.7.7/rofi-debugging.5.markdown
+    - Keys: 1.7.7/rofi-keys.5.markdown
+    - Thumbnails: 1.7.7/rofi-thumbnails.5.markdown
+  - 1.7.6:
+    - Rofi: 1.7.6/rofi.1.markdown 
+    - Themes: 1.7.6/rofi-theme.5.markdown
+    - Dmenu: 1.7.6/rofi-dmenu.5.markdown
+    - Script: 1.7.6/rofi-script.5.markdown
+    - Debugging: 1.7.6/rofi-debugging.5.markdown
+    - Keys: 1.7.6/rofi-keys.5.markdown
+    - Thumbnails: 1.7.6/rofi-thumbnails.5.markdown
   - 1.7.5:
     - Rofi: 1.7.5/rofi.1.markdown 
     - Themes: 1.7.5/rofi-theme.5.markdown
diff --git a/releasenotes/1.7.6/release-1.7.6.markdown b/releasenotes/1.7.6/release-1.7.6.markdown
index 122139102..fc31d09da 100644
--- a/releasenotes/1.7.6/release-1.7.6.markdown
+++ b/releasenotes/1.7.6/release-1.7.6.markdown
@@ -2,13 +2,13 @@
 
 ## Recursive file browser
 
-An experimental file browser is introduced in this version. This recursively scans through the 
-users home directory (this is configurable) to find files.
-Its designed to be asynchronous and very fast.
+An experimental file browser is introduced in this version.
+This recursively scans through the users home directory (this is configurable) to find files.
+It is designed to be asynchronous and very fast.
 
 The following settings can be configured:
 
-‘‘‘css
+```css
 configuration {
    recursivebrowser {
       /** Directory the file browser starts in. */
@@ -21,17 +21,21 @@ configuration {
       command: "xdg‐open";
    }
 }
-‘‘‘
+```
 
+A thumbnail generation mechanism is also supported if `-show-icons` is enabled.
+See details and setup in the `rofi-thumbnails(5)` man page. Thanks to giomatfois62 for
+bringing this feature to life!
 
 ## Copy to clipboard support
 
 Add support to copy current selected item to clipboard.
 The added `control-c` binding copies the current selection to the clipboard.
-THIS ONLY WORKS WITH CLIPBOARD MANAGER!!! Once rofi is closes, the data is
+
+**THIS ONLY WORKS WITH CLIPBOARD MANAGER!!!** Once rofi is closed, the data is
 gone!
-    
-## entry box history
+
+## Entry box history
 
 You can now recall and move through previous queries by using
 `kb-entry-history-up` or 'kb-entry-history-down` keys. (`Control-Up`,
@@ -39,28 +43,77 @@ You can now recall and move through previous queries by using
 
 The following settings can be configured:
 
-‘‘‘css
+```css
 configuration {
     entry  {
         max‐history: 30;
     }
 }
-‘‘‘
-
+```
 
 ## Fix calc
 
 There was a non-parsable grammar in the 'calc' part of the language.
 The % operator (modulo) overloaded with percent and could leave to statements
-having multiple valid but contradicting interpretations. To resolve this the modulo
-operator is now `modulo`. Including in this patch several smaller issues with the
-parser where fixed.
+having multiple valid but contradicting interpretations.
+To resolve this the modulo operator is now `modulo`.
+
+Several smaller issues with the parser were also fixed in this patch.
+
+## Text and cursor outline
+
+Three new properties were added to textbox widgets to control text outline:
+
+* `text-outline` boolean to enable outlines
+* `text-outline-width` to control size
+* `text-outline-color` to control color
+
+![Outlines](./text-outline.png)
+
+Outlines can also be added to cursors, via similarly named
+properties (`cursor-outline-*`).
+
+## Dependencies and packaging
 
-## Text outline
+In this version, we have bumped the minimal required versions of some
+dependencies to keep up with bugs and deprecations while staying compatible
+with long-term supported distributions.
+
+* glib: 2.72 or newer
+* meson: 0.59.0 or newer
+
+This roughly corresponds to Ubuntu 22.04 Jammy and Debian Bookworm.
+
+Generated man pages were removed from the git repository and now require
+`pandoc` to build instead of `go-md2man`. If you compile from git, you
+will now need to install `pandoc` to get the man pages.
+
+Release tarballs still contain the files and can be installed without
+additional tool.
+
+## Known issues
+
+* `new-selection` is not working for values exceeding the number of rows in previous run. (#2037)
+
+## Other smaller changes
+
+* new `.rasinc` extension for theme fragments included from other theme files
+* `-ellipsize-mode` mode option in dmenu mode can be set to `start`, `middle` or `end`
+  to control how long entries are ellipsized
+* `-list-keybindings` to print a summary of configured bindings
+* `-window-prefer-icon-theme` to force precedence of theme icons over applications'
+  custom ones (#1702)
+* `-placeholder-markup` to enable pango markup when rendering placeholder text (#1690)
+* `urgent` and `active` flags can be controlled for each row in dmenu and script
+  modes
+* `-transient-window-mode` to make rofi react like a modal dialog that is transient to
+  the currently focused window.
+* Fixing window coordinates for non-reparting window manager. (Thanks to Ortango #1969)
+* Fix failing decode of animated gif files. (Thanks to martinsifrar #1975)
 
 ## Website
 
-The current documentation is now also available on online at:
+The current documentation is now also available online at:
 [https://davatorium.github.io/rofi/](https://davatorium.github.io/rofi/)
 
 # Thanks to
@@ -77,26 +130,88 @@ Special thanks goes to:
   * Dimitris Triantafyllidis
   * duarm
   * Fabian Winter
+  * giomatfois62
   * Gutyina Gergő
   * Jasper Lievisse Adriaanse
   * Jorge
+  * martinsifrar
   * Martin Weinelt
   * Morgane Glidic
   * Naïm Favier
   * Nikita Zlobin
   * nomoo
   * notuxic
+  * Ortango
   * Rasmus Steinke
   * Tim Pope
   * TonCherAmi
   * vE5li
   * Yuta Katayama
   * Danny Colin
+  * xsy420
 
 Apologies if I mistyped or missed anybody.
 
 # Changelog
-
+* [CI] Fix CI build for updated runner.
+* [DOC] Add mouse button names to documentation.
+* [Doc] Clarify documentation for User Script directory. (#2043)
+* [Build] Add shadow to build system. (#2042, #2036)
+* [Textbox] Use FontMetrics font height (if available) to get height
+* [Theme] Fixes recursion in double_inside
+* Try to support modifiers in XIM again (#2015)
+* [autoconf] Fix missing dependency.
+* Better XIM interaction by filtering modifiers (#2000)
+* Fix ime and enable build option (#1999)
+* [Autotools] Ship missing files for meson build
+* Fix some compiler warnings
+* #1995: Disable history in password mode, move disabling into create_view.
+* [config] Set filebrowser as default completer.
+* [WIP] xdg thumbnails fetching with fallback on mimetype icons (#1939)
+* Add -transient-window mode (#1988)
+* Fix scrolling for vertical layout with horizontal packing
+* Place continuous scroll center in middle column
+* [Script] Fix keep-selection add keep-filter
+* [RecursiveBrowser] Make implementation not recursive.
+* [xcb] Add border_width to window coordinates (#1969)
+* [IconFetcher] Don't check for extension for image file
+* [IconFetcher] Fix failing decode of animated GIFs. (#1975)
+* [Doc] Fix typos, thx to @Nickwiz
+* [Run] Don't re-quote history items.
+* [Modes] Remove dead code in mode implems (#1960)
+* [View] Work around GThreadPool 1 pointer bug.
+* Also fix typo in icon fetcher.
+* [Github] Bump checkout to v4
+* [Doc] Switch to pandoc and remove generated files (#1955)
+* [Build] Add missing dist files from libnkutils
+* [IconFetcher] Don't free on removal from thread-pool
+* Add an item-free method to the thread-pool
+* [Window] write code so clang-check does not complain about leak.
+* [script|dmenu] Add option to make row permanent. (#1952)
+* [run] fix missing doxygen and add explanation.
+* [Run] When passing raw entry, pass it unquoted to history (#1951)
+* Replace deprecated g_memdup by g_memdup2
+* Bump glib version to 2.72
+* [Build] Bump minimal meson version to 0.59.0 (#1947)
+* Fix compiler warnings in window mode.
+* Fix some compiler warnings.
+* [RUN] shell escape command before processing it further.
+* [DRun] Drun read url field from cache.
+* [Build] Reduce amount of warnings (#1944)
+* [View] Don't use xcb surface to render to png, but create surface.
+* [Box] When estimating height, set correct width on children (#1943)
+* [ThreadPool] Sort items in the queue based on priority
+* [Doc] Fix broken ``` guards.
+* [Doc] Remove reddit link from config.yml.
+* [Doc] Clarify in build instructions what release to use.
+* Add extra documentation issue template.
+* Fix typo in dynamic_themes.md (#1941)
+* [DOC] Add explanation to PATTERN of brackets (#1933)
+* [Doc] Update manpage to clarify meta property.
+* [View] On mode switch force refilter instead of queuing. (#1928)
+* [View] Allow float delay (#1926)
+* [View] Always forward motion to the grabbed widget first.
+* [IconFetcher] If last step fails to load icon, don't error out make warning
 * [Script] Update theme property clarification a bit.
 * [Script] Add clarification to theme property.
 * [Dmenu][Script] Add 'display' row option to override whats displayed.
diff --git a/releasenotes/1.7.6/text-outline.png b/releasenotes/1.7.6/text-outline.png
new file mode 100644
index 000000000..10128c32f
Binary files /dev/null and b/releasenotes/1.7.6/text-outline.png differ
diff --git a/releasenotes/1.7.7/release-1.7.7.markdown b/releasenotes/1.7.7/release-1.7.7.markdown
new file mode 100644
index 000000000..46dd46034
--- /dev/null
+++ b/releasenotes/1.7.7/release-1.7.7.markdown
@@ -0,0 +1,83 @@
+# 1.7.7: Time Dilation
+
+A quick-fix release following reports after releasing the 1.7.6 release.
+
+## Issues
+
+### Drawing issue
+
+After the previous release some users experienced rofi being rendered to screen
+as a black box. The issue seems to be only hit on certain video cards/drivers
+see the github issue [#2068](https://github.com/davatorium/rofi/issues/2068).It turned out on these systems using
+`cairo_push/pop_group` results in a black screen when the backing surface is
+using the XCB library. When using other drivers, or rendering to a cairo image
+surface.
+Hopefully reverting to `cairo_store` and `cairo_restore` fixes this issue for everybody.
+
+Issue [#2068](https://github.com/davatorium/rofi/issues/2068)
+
+### Window mode missing some windows
+
+Because of a wrong check some windows where misidentified as 'skip pager' and
+hidden from the view. This should now be resolved.
+
+Issue [#2071](https://github.com/davatorium/rofi/issues/2071)
+
+### 'Character' in config file broken
+
+A previous patch to make using strings more easy to use in the configuration
+file broke settings that use the 'character' type as setting. Because not a lot
+of options use the 'Character' type , this has been 'resolved' by using the
+'String' type and picking the first ASCII character. 
+
+Issue [#2070](https://github.com/davatorium/rofi/issues/2070)
+
+## improvements
+
+Beside these issues, also some improvements are included in this release. 
+
+## Resolve 'rasinc' for @imports
+
+When importing a theme file like this:
+
+```css
+@import "mytheme"
+```
+
+Rofi would find any file 'mytheme.rasi' in any of the theme paths.
+This was missing the new extension for shared include files 'rasinc'.
+This is now added when resolving.
+
+Issue [#2069](https://github.com/davatorium/rofi/issues/2069)
+
+## Desktop file DBus activation
+
+Some desktop files did not launch correctly because it did not implement the
+DBusActivation feature. While most desktop files did provide a fallback `Exec`
+entry, this seems to not always be the case. Rofi should now first try
+DBusActivation and fall back to the Exec if it does not succeed.
+
+Issue [#1924](https://github.com/davatorium/rofi/issues/1924)
+
+## Resolve `-config` identical to `-theme`
+
+if you pass an alternative config file, this is now resolved using the same
+logic as the `-theme` argument. Making it easier to have multiple, alternative,
+configuration files.
+
+Issue [#2040](https://github.com/davatorium/rofi/issues/2040)
+
+## Changelog
+
+* [Widget] Don't use cairo_push/pop_group as it causes issues. (#2068)
+* Revert "[window] Check bitmask, not full comparison".  (#2071)
+* [Config] Remove character data type as it aliases with string. (#2070)
+* [Doc] Refer to releasenotes for updates in Changelog file. (#2069)
+* [Doc] Update theme documentation with import resolving update. (#2069)
+* [Themes] Update themes to import without rasi(nc) extensions. (#2069)
+* [Theme] Fix resolving of 'rasinc' extension when no extension is given. (#2069)
+* Be more diligent trying to resolve -config. (#2040)
+* Use FALSE instead of FALSE.
+* Resolve -config argument identical to a -theme argument. (#2040)
+* [DRun] If indicated by .desktop file, launch via dbus activation. (#1924)
+* [Website] Update website links and headers.
diff --git a/source/helper.c b/source/helper.c
index ea1788307..b4cd9b606 100644
--- a/source/helper.c
+++ b/source/helper.c
@@ -27,11 +27,12 @@
  */
 
 /** The log domain for this helper. */
+#include "config.h"
 #define G_LOG_DOMAIN "Helper"
 
-#include "config.h"
 #include "display.h"
 #include "helper-theme.h"
+#include "helper.h"
 #include "rofi.h"
 #include "settings.h"
 #include "view.h"
@@ -139,6 +140,7 @@ static gchar *glob_to_regex(const char *input) {
   return r;
 }
 static gchar *fuzzy_to_regex(const char *input) {
+  char *retv = NULL;
   GString *str = g_string_new("");
   gchar *r = g_regex_escape_string(input, -1);
   gchar *iter;
@@ -162,8 +164,7 @@ static gchar *fuzzy_to_regex(const char *input) {
     first = 0;
   }
   g_free(r);
-  char *retv = str->str;
-  g_string_free(str, FALSE);
+  retv = g_string_free(str, FALSE);
   return retv;
 }
 
@@ -1065,37 +1066,14 @@ gboolean helper_execute_command(const char *wd, const char *cmd,
   return helper_execute(wd, args, "", cmd, context);
 }
 
-char *helper_get_theme_path(const char *file, const char **ext,
-                            const char *parent_file) {
+static char *helper_get_theme_path_check_file(const char *filename,
+                                              const char *parent_file) {
 
-  char *filename = rofi_expand_path(file);
-  g_debug("Opening theme, testing: %s\n", filename);
-  if (g_path_is_absolute(filename)) {
-    g_debug("Opening theme, path is absolute: %s", filename);
-    if (g_file_test(filename, G_FILE_TEST_EXISTS)) {
-      return filename;
-    }
-  }
-  gboolean ext_found = FALSE;
-  for (const char **i = ext; *i != NULL; i++) {
-    if (g_str_has_suffix(file, *i)) {
-      ext_found = TRUE;
-      break;
-    }
-  }
-  if (ext_found) {
-    filename = rofi_expand_path(file);
-  } else {
-    g_assert_nonnull(ext[0]);
-    char *temp = filename;
-    // TODO: Pick the first extension. needs fixing.
-    filename = g_strconcat(temp, ext[0], NULL);
-    g_free(temp);
-  }
+  // Check if absolute path.
   if (g_path_is_absolute(filename)) {
     g_debug("Opening theme, path is absolute: %s", filename);
     if (g_file_test(filename, G_FILE_TEST_EXISTS)) {
-      return filename;
+      return g_strdup(filename);
     }
     g_debug("Opening theme, path is absolute but does not exists: %s",
             filename);
@@ -1107,7 +1085,6 @@ char *helper_get_theme_path(const char *file, const char **ext,
       g_free(basedir);
       g_debug("Opening theme, check in dir where file is included: %s", path);
       if (g_file_test(path, G_FILE_TEST_EXISTS)) {
-        g_free(filename);
         return path;
       }
       g_debug("Opening theme, file does not exists in dir where file is "
@@ -1115,14 +1092,12 @@ char *helper_get_theme_path(const char *file, const char **ext,
               filename);
     }
   }
-
   // Check config's themes directory.
   const char *cpath = g_get_user_config_dir();
   if (cpath) {
     char *themep = g_build_filename(cpath, "rofi", "themes", filename, NULL);
     g_debug("Opening theme, testing: %s", themep);
     if (themep && g_file_test(themep, G_FILE_TEST_EXISTS)) {
-      g_free(filename);
       return themep;
     }
     g_free(themep);
@@ -1132,7 +1107,6 @@ char *helper_get_theme_path(const char *file, const char **ext,
     char *themep = g_build_filename(cpath, "rofi", filename, NULL);
     g_debug("Opening theme, testing: %s", themep);
     if (g_file_test(themep, G_FILE_TEST_EXISTS)) {
-      g_free(filename);
       return themep;
     }
     g_free(themep);
@@ -1144,7 +1118,6 @@ char *helper_get_theme_path(const char *file, const char **ext,
     if (theme_path) {
       g_debug("Opening theme, testing: %s", theme_path);
       if (g_file_test(theme_path, G_FILE_TEST_EXISTS)) {
-        g_free(filename);
         return theme_path;
       }
       g_free(theme_path);
@@ -1161,7 +1134,6 @@ char *helper_get_theme_path(const char *file, const char **ext,
       if (theme_path) {
         g_debug("Opening theme, testing: %s", theme_path);
         if (g_file_test(theme_path, G_FILE_TEST_EXISTS)) {
-          g_free(filename);
           return theme_path;
         }
         g_free(theme_path);
@@ -1173,11 +1145,55 @@ char *helper_get_theme_path(const char *file, const char **ext,
   if (theme_path) {
     g_debug("Opening theme, testing: %s", theme_path);
     if (g_file_test(theme_path, G_FILE_TEST_EXISTS)) {
-      g_free(filename);
       return theme_path;
     }
     g_free(theme_path);
   }
+  return NULL;
+}
+
+char *helper_get_theme_path(const char *file, const char **ext,
+                            const char *parent_file) {
+
+  char *filename = rofi_expand_path(file);
+  g_debug("Opening theme, testing: %s\n", filename);
+  if (g_path_is_absolute(filename)) {
+    g_debug("Opening theme, path is absolute: %s", filename);
+    if (g_file_test(filename, G_FILE_TEST_EXISTS)) {
+      return filename;
+    }
+  }
+  gboolean ext_found = FALSE;
+  for (const char **i = ext; *i != NULL; i++) {
+    if (g_str_has_suffix(file, *i)) {
+      ext_found = TRUE;
+      break;
+    }
+  }
+  if (ext_found) {
+    filename = rofi_expand_path(file);
+
+    char *retv = helper_get_theme_path_check_file(filename, parent_file);
+    if (retv) {
+      g_free(filename);
+      return retv;
+    }
+  } else {
+    g_assert_nonnull(ext[0]);
+    // Iterate through extensions.
+    char *temp = filename;
+    for (const char **i = ext; *i != NULL; i++) {
+      filename = g_strconcat(temp, *i, NULL);
+      char *retv = helper_get_theme_path_check_file(filename, parent_file);
+      if (retv) {
+        g_free(filename);
+        g_free(temp);
+        return retv;
+      }
+    }
+    g_free(temp);
+  }
+
   return filename;
 }
 
diff --git a/source/modes/drun.c b/source/modes/drun.c
index 17ad049b8..b485e29c6 100644
--- a/source/modes/drun.c
+++ b/source/modes/drun.c
@@ -25,10 +25,11 @@
  *
  */
 
-/** The log domain of this dialog. */
 #define G_LOG_DOMAIN "Modes.DRun"
-
 #include "config.h"
+/** The log domain of this dialog. */
+#include "glib.h"
+
 #ifdef ENABLE_DRUN
 #include <limits.h>
 #include <stdio.h>
@@ -44,6 +45,8 @@
 #include <sys/types.h>
 #include <unistd.h>
 
+#include <gio/gio.h>
+
 #include "display.h"
 #include "helper.h"
 #include "history.h"
@@ -330,6 +333,89 @@ static void launch_link_entry(DRunModeEntry *e) {
     g_free(path);
   }
 }
+static gchar *app_path_for_id(const gchar *app_id) {
+  gchar *path;
+  gint i;
+
+  path = g_strconcat("/", app_id, NULL);
+  for (i = 0; path[i]; i++) {
+    if (path[i] == '.')
+      path[i] = '/';
+    if (path[i] == '-')
+      path[i] = '_';
+  }
+
+  return path;
+}
+static GVariant *app_get_platform_data(void) {
+  GVariantBuilder builder;
+  const gchar *startup_id;
+
+  g_variant_builder_init(&builder, G_VARIANT_TYPE_VARDICT);
+
+  if ((startup_id = g_getenv("DESKTOP_STARTUP_ID")))
+    g_variant_builder_add(&builder, "{sv}", "desktop-startup-id",
+                          g_variant_new_string(startup_id));
+
+  if ((startup_id = g_getenv("XDG_ACTIVATION_TOKEN")))
+    g_variant_builder_add(&builder, "{sv}", "activation-token",
+                          g_variant_new_string(startup_id));
+
+  return g_variant_builder_end(&builder);
+}
+
+static gboolean exec_dbus_entry(DRunModeEntry *e, const char *path) {
+  GVariantBuilder files;
+  GDBusConnection *session;
+  GError *error = NULL;
+  gchar *object_path;
+  GVariant *result;
+  GVariant *params = NULL;
+  const char *method = "Activate";
+  g_debug("Trying to launch desktop file using dbus activation.");
+
+  session = g_bus_get_sync(G_BUS_TYPE_SESSION, NULL, &error);
+  if (!session) {
+    g_warning("unable to connect to D-Bus: %s\n", error->message);
+    g_error_free(error);
+    return FALSE;
+  }
+
+  object_path = app_path_for_id(e->app_id);
+
+  g_variant_builder_init(&files, G_VARIANT_TYPE_STRING_ARRAY);
+
+  if (path != NULL) {
+    method = "Open";
+    params = g_variant_new("(as@a{sv})", &files, app_get_platform_data());
+  } else {
+    params = g_variant_new("(@a{sv})", app_get_platform_data());
+  }
+  if (path) {
+    GFile *file = g_file_new_for_commandline_arg(path);
+    g_variant_builder_add_value(
+        &files, g_variant_new_take_string(g_file_get_uri(file)));
+    g_object_unref(file);
+  }
+  result = g_dbus_connection_call_sync(
+      session, e->app_id, object_path, "org.freedesktop.Application", method,
+      params, G_VARIANT_TYPE_UNIT, G_DBUS_CALL_FLAGS_NONE, -1, NULL, &error);
+
+  g_free(object_path);
+
+  if (result) {
+    g_variant_unref(result);
+  } else {
+    g_warning("error sending %s message to application: %s\n", "Open",
+              error->message);
+    g_error_free(error);
+    g_object_unref(session);
+    return FALSE;
+  }
+  g_object_unref(session);
+  return TRUE;
+}
+
 static void exec_cmd_entry(DRunModeEntry *e, const char *path) {
   GError *error = NULL;
   GRegex *reg = g_regex_new("%[a-zA-Z%]", 0, 0, &error);
@@ -399,15 +485,26 @@ static void exec_cmd_entry(DRunModeEntry *e, const char *path) {
         g_key_file_get_string(e->key_file, e->action, "StartupWMClass", NULL);
   }
 
-  // Returns false if not found, if key not found, we don't want run in
-  // terminal.
-  gboolean terminal =
-      g_key_file_get_boolean(e->key_file, e->action, "Terminal", NULL);
-  if (helper_execute_command(exec_path, fp, terminal, sn ? &context : NULL)) {
-    char *drun_cach_path = g_build_filename(cache_dir, DRUN_CACHE_FILE, NULL);
-    // Store it based on the unique identifiers (desktop_id).
-    history_set(drun_cach_path, e->desktop_id);
-    g_free(drun_cach_path);
+  /**
+   * If its required to launch via dbus, do that.
+   */
+  gboolean launched = FALSE;
+  if (g_key_file_get_boolean(e->key_file, e->action, "DBusActivatable", NULL)) {
+    launched = exec_dbus_entry(e, path);
+  }
+  if (launched == FALSE) {
+    /** Fallback to old style if not set. */
+
+    // Returns false if not found, if key not found, we don't want run in
+    // terminal.
+    gboolean terminal =
+        g_key_file_get_boolean(e->key_file, e->action, "Terminal", NULL);
+    if (helper_execute_command(exec_path, fp, terminal, sn ? &context : NULL)) {
+      char *drun_cach_path = g_build_filename(cache_dir, DRUN_CACHE_FILE, NULL);
+      // Store it based on the unique identifiers (desktop_id).
+      history_set(drun_cach_path, e->desktop_id);
+      g_free(drun_cach_path);
+    }
   }
   g_free(wmclass);
   g_free(exec_path);
diff --git a/source/modes/help-keys.c b/source/modes/help-keys.c
index 0b8a565ab..af3519a12 100644
--- a/source/modes/help-keys.c
+++ b/source/modes/help-keys.c
@@ -46,7 +46,9 @@
 #include "xrmoptions.h"
 
 typedef struct {
+  /** array of strings containing key descriptions */
   char **messages;
+  /** lengths of the messages array */
   unsigned int messages_length;
 } KeysHelpModePrivateData;
 
@@ -118,5 +120,5 @@ Mode help_keys_mode = {.name = "keys",
                        ._get_completion = NULL,
                        ._get_display_value = _get_display_value,
                        .private_data = NULL,
-		       .free = NULL,
-		       .type = MODE_TYPE_SWITCHER };
+                       .free = NULL,
+                       .type = MODE_TYPE_SWITCHER};
diff --git a/source/modes/window.c b/source/modes/window.c
index 8b8804b5f..6b6d504cf 100644
--- a/source/modes/window.c
+++ b/source/modes/window.c
@@ -298,7 +298,7 @@ window_get_attributes(xcb_window_t w) {
 // _NET_WM_STATE_*
 static int client_has_state(client *c, xcb_atom_t state) {
   for (int i = 0; i < c->states; i++) {
-    if ((c->state[i] & state) == state) {
+    if (c->state[i] == state) {
       return 1;
     }
   }
diff --git a/source/rofi-icon-fetcher.c b/source/rofi-icon-fetcher.c
index 7562dc9b9..8b66600f2 100644
--- a/source/rofi-icon-fetcher.c
+++ b/source/rofi-icon-fetcher.c
@@ -50,9 +50,10 @@
 #include "helper.h"
 #include <gdk-pixbuf/gdk-pixbuf.h>
 
-// thumbnailers key file's group and file extension
+/** Desktop entry specifying the thumbnailer. */
 #define THUMBNAILER_ENTRY_GROUP "Thumbnailer Entry"
-#define THUMBNAILER_EXTENSION   ".thumbnailer"
+/** Extension used for the thumbnailer. */
+#define THUMBNAILER_EXTENSION ".thumbnailer"
 
 typedef struct {
   // Context for icon-themes.
@@ -66,7 +67,7 @@ typedef struct {
   // list extensions
   GList *supported_extensions;
   uint32_t last_uid;
-  
+
   // thumbnailers per mime-types hashmap
   GHashTable *thumbnailers;
 } IconFetcher;
@@ -105,14 +106,14 @@ static void rofi_icon_fetcher_load_thumbnailers(const gchar *path) {
   gchar *thumb_path = g_build_filename(path, "thumbnailers", NULL);
 
   GDir *dir = g_dir_open(thumb_path, 0, NULL);
-  
+
   if (!dir) {
     g_free(thumb_path);
     return;
   }
 
   const gchar *dirent;
-  
+
   while ((dirent = g_dir_read_name(dir))) {
     if (!g_str_has_suffix(dirent, THUMBNAILER_EXTENSION))
       continue;
@@ -125,28 +126,28 @@ static void rofi_icon_fetcher_load_thumbnailers(const gchar *path) {
       g_warning("Error loading thumbnailer %s: %s", filename, error->message);
       g_error_free(error);
     } else {
-      gchar *command = g_key_file_get_string(
-        key_file, THUMBNAILER_ENTRY_GROUP, "Exec", NULL);
+      gchar *command = g_key_file_get_string(key_file, THUMBNAILER_ENTRY_GROUP,
+                                             "Exec", NULL);
       gchar **mime_types = g_key_file_get_string_list(
-        key_file, THUMBNAILER_ENTRY_GROUP, "MimeType", NULL, NULL);
+          key_file, THUMBNAILER_ENTRY_GROUP, "MimeType", NULL, NULL);
 
       if (mime_types && command) {
         guint i;
         for (i = 0; mime_types[i] != NULL; i++) {
-          if (!g_hash_table_lookup(
-              rofi_icon_fetcher_data->thumbnailers, mime_types[i])) {
-            g_info("Loading thumbnailer %s for mimetype %s", filename, mime_types[i]);
-            g_hash_table_insert(
-              rofi_icon_fetcher_data->thumbnailers,
-              g_strdup(mime_types[i]),
-              g_strdup(command)
-            );
+          if (!g_hash_table_lookup(rofi_icon_fetcher_data->thumbnailers,
+                                   mime_types[i])) {
+            g_info("Loading thumbnailer %s for mimetype %s", filename,
+                   mime_types[i]);
+            g_hash_table_insert(rofi_icon_fetcher_data->thumbnailers,
+                                g_strdup(mime_types[i]), g_strdup(command));
           }
         }
       }
 
-      if (mime_types) g_strfreev(mime_types);
-      if (command) g_free(command);
+      if (mime_types)
+        g_strfreev(mime_types);
+      if (command)
+        g_free(command);
     }
 
     g_key_file_free(key_file);
@@ -157,26 +158,25 @@ static void rofi_icon_fetcher_load_thumbnailers(const gchar *path) {
   g_free(thumb_path);
 }
 
-static gchar** setup_thumbnailer_command(const gchar *command,
+static gchar **setup_thumbnailer_command(const gchar *command,
                                          const gchar *filename,
                                          const gchar *encoded_uri,
-                                         const gchar *output_path,
-                                         int size) {
+                                         const gchar *output_path, int size) {
   gchar **command_parts = g_strsplit(command, " ", 0);
   guint command_parts_count = g_strv_length(command_parts);
-  
-  gchar **command_args = NULL; 
-  
+
+  gchar **command_args = NULL;
+
   if (command_parts) {
-    command_args = g_malloc0(sizeof(gchar*) * (command_parts_count + 3 + 1));
-    
+    command_args = g_malloc0(sizeof(gchar *) * (command_parts_count + 3 + 1));
+
     // set process niceness value to 19 (low priority)
     guint current_index = 0;
-    
+
     command_args[current_index++] = g_strdup("nice");
     command_args[current_index++] = g_strdup("-n");
     command_args[current_index++] = g_strdup("19");
-    
+
     // add executable and arguments of the thumbnailer to the list
     guint i;
     for (i = 0; command_parts[i] != NULL; i++) {
@@ -197,7 +197,7 @@ static gchar** setup_thumbnailer_command(const gchar *command,
 
     g_strfreev(command_parts);
   }
-  
+
   return command_args;
 }
 
@@ -206,8 +206,9 @@ static gboolean exec_thumbnailer_command(gchar **command_args) {
   gint wait_status;
   GError *error = NULL;
 
-  gboolean spawned = g_spawn_sync(NULL, command_args,
-    NULL, G_SPAWN_DEFAULT | G_SPAWN_SEARCH_PATH, NULL, NULL, NULL, NULL, &wait_status, &error);
+  gboolean spawned = g_spawn_sync(NULL, command_args, NULL,
+                                  G_SPAWN_DEFAULT | G_SPAWN_SEARCH_PATH, NULL,
+                                  NULL, NULL, NULL, &wait_status, &error);
 
   if (spawned) {
     return g_spawn_check_wait_status(wait_status, NULL);
@@ -226,22 +227,22 @@ static gboolean rofi_icon_fetcher_create_thumbnail(const gchar *mime_type,
                                                    int size) {
   gboolean thumbnail_created = FALSE;
 
-  gchar *command = g_hash_table_lookup(
-    rofi_icon_fetcher_data->thumbnailers, mime_type);
+  gchar *command =
+      g_hash_table_lookup(rofi_icon_fetcher_data->thumbnailers, mime_type);
 
   if (!command) {
     return thumbnail_created;
   }
 
-  // split command string to isolate arguments and expand them in a list  
+  // split command string to isolate arguments and expand them in a list
   gchar **command_args = setup_thumbnailer_command(
-    command, filename, encoded_uri, output_path, size);
-  
+      command, filename, encoded_uri, output_path, size);
+
   if (command_args) {
-    thumbnail_created = exec_thumbnailer_command(command_args);    
+    thumbnail_created = exec_thumbnailer_command(command_args);
     g_strfreev(command_args);
   }
-  
+
   return thumbnail_created;
 }
 
@@ -301,19 +302,19 @@ void rofi_icon_fetcher_init(void) {
     g_free(exts);
   }
   g_slist_free(l);
-  
+
   // load available thumbnailers from system dirs and user dir
   rofi_icon_fetcher_data->thumbnailers = g_hash_table_new_full(
-    g_str_hash, g_str_equal, (GDestroyNotify)g_free, (GDestroyNotify)g_free);
+      g_str_hash, g_str_equal, (GDestroyNotify)g_free, (GDestroyNotify)g_free);
 
-  const gchar * const *system_data_dirs = g_get_system_data_dirs();
+  const gchar *const *system_data_dirs = g_get_system_data_dirs();
   const gchar *user_data_dir = g_get_user_data_dir();
 
   rofi_icon_fetcher_load_thumbnailers(user_data_dir);
 
   guint i;
   for (i = 0; system_data_dirs[i] != NULL; i++) {
-      rofi_icon_fetcher_load_thumbnailers(system_data_dirs[i]);
+    rofi_icon_fetcher_load_thumbnailers(system_data_dirs[i]);
   }
 }
 
@@ -325,7 +326,7 @@ void rofi_icon_fetcher_destroy(void) {
   if (rofi_icon_fetcher_data == NULL) {
     return;
   }
-  
+
   g_hash_table_unref(rofi_icon_fetcher_data->thumbnailers);
 
   nk_xdg_theme_context_free(rofi_icon_fetcher_data->xdg_context);
@@ -459,39 +460,38 @@ gboolean rofi_icon_fetcher_file_is_image(const char *const path) {
 }
 
 // build thumbnail's path using md5 hash of an entry name
-static gchar* rofi_icon_fetcher_get_thumbnail(gchar* name, 
-                                              int requested_size, 
+static gchar *rofi_icon_fetcher_get_thumbnail(gchar *name, int requested_size,
                                               int *thumb_size) {
   // calc entry_name md5 hash
-  GChecksum* checksum = g_checksum_new(G_CHECKSUM_MD5);
-  g_checksum_update(checksum, (guchar*)name, -1);
+  GChecksum *checksum = g_checksum_new(G_CHECKSUM_MD5);
+  g_checksum_update(checksum, (guchar *)name, -1);
   const gchar *md5_hex = g_checksum_get_string(checksum);
 
   // determine thumbnail folder based on the request size
-  const gchar* cache_dir = g_get_user_cache_dir();
-  gchar* thumb_dir;
-  gchar* thumb_path;
+  const gchar *cache_dir = g_get_user_cache_dir();
+  gchar *thumb_dir;
+  gchar *thumb_path;
 
   if (requested_size <= 128) {
     *thumb_size = 128;
     thumb_dir = g_strconcat(cache_dir, "/thumbnails/normal/", NULL);
-    thumb_path = g_strconcat(cache_dir, "/thumbnails/normal/",
-        md5_hex, ".png", NULL);
+    thumb_path =
+        g_strconcat(cache_dir, "/thumbnails/normal/", md5_hex, ".png", NULL);
   } else if (requested_size <= 256) {
     *thumb_size = 256;
     thumb_dir = g_strconcat(cache_dir, "/thumbnails/large/", NULL);
-    thumb_path = g_strconcat(cache_dir, "/thumbnails/large/",
-        md5_hex, ".png", NULL);
+    thumb_path =
+        g_strconcat(cache_dir, "/thumbnails/large/", md5_hex, ".png", NULL);
   } else if (requested_size <= 512) {
     *thumb_size = 512;
     thumb_dir = g_strconcat(cache_dir, "/thumbnails/x-large/", NULL);
-    thumb_path = g_strconcat(cache_dir, "/thumbnails/x-large/",
-        md5_hex, ".png", NULL);
+    thumb_path =
+        g_strconcat(cache_dir, "/thumbnails/x-large/", md5_hex, ".png", NULL);
   } else {
     *thumb_size = 1024;
     thumb_dir = g_strconcat(cache_dir, "/thumbnails/xx-large/", NULL);
-    thumb_path = g_strconcat(cache_dir, "/thumbnails/xx-large/",
-        md5_hex, ".png", NULL);
+    thumb_path =
+        g_strconcat(cache_dir, "/thumbnails/xx-large/", md5_hex, ".png", NULL);
   }
 
   // create thumbnail directory if it does not exist
@@ -504,24 +504,24 @@ static gchar* rofi_icon_fetcher_get_thumbnail(gchar* name,
 }
 
 // retrieves icon key from a .desktop file
-static gchar* rofi_icon_fetcher_get_desktop_icon(const gchar* file_path) {
+static gchar *rofi_icon_fetcher_get_desktop_icon(const gchar *file_path) {
   GKeyFile *kf = g_key_file_new();
   GError *key_error = NULL;
   gchar *icon_key = NULL;
-  
+
   gboolean res = g_key_file_load_from_file(kf, file_path, 0, &key_error);
-  
+
   if (res) {
     icon_key = g_key_file_get_string(kf, "Desktop Entry", "Icon", NULL);
   } else {
-    g_debug("Failed to parse desktop file %s because: %s.",
-        file_path, key_error->message);
-    
+    g_debug("Failed to parse desktop file %s because: %s.", file_path,
+            key_error->message);
+
     g_error_free(key_error);
   }
-  
+
   g_key_file_free(kf);
-  
+
   return icon_key;
 }
 
@@ -539,13 +539,13 @@ static void rofi_icon_fetcher_worker(thread_state *sdata,
   if (g_str_has_prefix(sentry->entry->name, "thumbnail://")) {
     // remove uri thumbnail prefix from entry name
     gchar *entry_name = &sentry->entry->name[12];
-    
+
     if (strcmp(entry_name, "") == 0) {
       sentry->query_done = TRUE;
       rofi_view_reload();
       return;
     }
-    
+
     // use custom user command to generate the thumbnail
     if (config.preview_cmd != NULL) {
       int requested_size = MAX(sentry->wsize, sentry->hsize);
@@ -553,19 +553,18 @@ static void rofi_icon_fetcher_worker(thread_state *sdata,
 
       icon_path = icon_path_ = rofi_icon_fetcher_get_thumbnail(
           entry_name, requested_size, &thumb_size);
-      
+
       if (!g_file_test(icon_path, G_FILE_TEST_EXISTS)) {
         char **command_args = NULL;
         int argsv = 0;
         gchar *size_str = g_strdup_printf("%d", thumb_size);
-        
-        helper_parse_setup(
-          config.preview_cmd, &command_args, &argsv,
-          "{input}", entry_name,
-          "{output}", icon_path_, "{size}", size_str, NULL);
+
+        helper_parse_setup(config.preview_cmd, &command_args, &argsv, "{input}",
+                           entry_name, "{output}", icon_path_, "{size}",
+                           size_str, NULL);
 
         g_free(size_str);
-        
+
         if (command_args) {
           exec_thumbnailer_command(command_args);
           g_strfreev(command_args);
@@ -576,13 +575,13 @@ static void rofi_icon_fetcher_worker(thread_state *sdata,
       if (g_str_has_suffix(entry_name, ".desktop")) {
         // if the entry is a .desktop file try to read its icon key
         gchar *icon_key = rofi_icon_fetcher_get_desktop_icon(entry_name);
-        
+
         if (icon_key == NULL || strlen(icon_key) == 0) {
           // no icon in .desktop file, fallback on mimetype icon (text/plain)
           icon_path = icon_path_ = nk_xdg_theme_get_icon(
-            rofi_icon_fetcher_data->xdg_context, themes, NULL, "text-plain",
-            MIN(sentry->wsize, sentry->hsize), 1, TRUE);
-          
+              rofi_icon_fetcher_data->xdg_context, themes, NULL, "text-plain",
+              MIN(sentry->wsize, sentry->hsize), 1, TRUE);
+
           g_free(icon_key);
         } else if (g_path_is_absolute(icon_key)) {
           // icon in .desktop file is an absolute path to an image
@@ -590,9 +589,9 @@ static void rofi_icon_fetcher_worker(thread_state *sdata,
         } else {
           // icon in .desktop file is a standard icon name
           icon_path = icon_path_ = nk_xdg_theme_get_icon(
-            rofi_icon_fetcher_data->xdg_context, themes, NULL, icon_key,
-            MIN(sentry->wsize, sentry->hsize), 1, TRUE);
-          
+              rofi_icon_fetcher_data->xdg_context, themes, NULL, icon_key,
+              MIN(sentry->wsize, sentry->hsize), 1, TRUE);
+
           g_free(icon_key);
         }
       } else {
@@ -603,40 +602,40 @@ static void rofi_icon_fetcher_worker(thread_state *sdata,
 
         // look for file thumbnail in appropriate folder based on requested size
         icon_path = icon_path_ = rofi_icon_fetcher_get_thumbnail(
-          encoded_uri, requested_size, &thumb_size);
+            encoded_uri, requested_size, &thumb_size);
 
         if (!g_file_test(icon_path, G_FILE_TEST_EXISTS)) {
           // try to generate thumbnail
           char *content_type = g_content_type_guess(entry_name, NULL, 0, NULL);
           char *mime_type = g_content_type_get_mime_type(content_type);
-          
+
           if (mime_type) {
             gboolean created = rofi_icon_fetcher_create_thumbnail(
-              mime_type, entry_name, encoded_uri, icon_path_, thumb_size);
+                mime_type, entry_name, encoded_uri, icon_path_, thumb_size);
 
             if (!created) {
               // replace forward slashes with minus sign to get the icon's name
               int index = 0;
 
-              while(mime_type[index]) {
-                 if(mime_type[index] == '/')
-                    mime_type[index] = '-';
-                 index++;
+              while (mime_type[index]) {
+                if (mime_type[index] == '/')
+                  mime_type[index] = '-';
+                index++;
               }
-              
+
               g_free(icon_path_);
 
               // try to fetch the mime-type icon
               icon_path = icon_path_ = nk_xdg_theme_get_icon(
-                rofi_icon_fetcher_data->xdg_context, themes, NULL, mime_type,
-                MIN(sentry->wsize, sentry->hsize), 1, TRUE);
+                  rofi_icon_fetcher_data->xdg_context, themes, NULL, mime_type,
+                  MIN(sentry->wsize, sentry->hsize), 1, TRUE);
             }
-            
+
             g_free(mime_type);
             g_free(content_type);
           }
         }
-        
+
         g_free(encoded_uri);
       }
     }
diff --git a/source/rofi-types.c b/source/rofi-types.c
index b9f752e28..cebd1ca05 100644
--- a/source/rofi-types.c
+++ b/source/rofi-types.c
@@ -10,8 +10,6 @@ const char *const PropertyTypeName[P_NUM_TYPES] = {
     "Double",
     /** String */
     "String",
-    /** Character */
-    "Character",
     /** Boolean */
     "Boolean",
     /** Color */
diff --git a/source/rofi.c b/source/rofi.c
index 9899b0f9c..642968c0e 100644
--- a/source/rofi.c
+++ b/source/rofi.c
@@ -79,6 +79,8 @@
 char *pidfile = NULL;
 /** Location of Cache directory. */
 const char *cache_dir = NULL;
+/** if the cache_dir string is allocated, keep pointer here so it can be freed.
+ */
 char *cache_dir_alloc = NULL;
 
 /** List of error messages.*/
@@ -1098,11 +1100,20 @@ int main(int argc, char *argv[]) {
       g_free(etc);
     }
 
-    if (config_path && g_file_test(config_path, G_FILE_TEST_IS_REGULAR)) {
-      if (rofi_theme_parse_file(config_path)) {
-        rofi_theme_free(rofi_theme);
-        rofi_theme = NULL;
+    if (config_path) {
+      // Try to resolve the path.
+      extern const char *rasi_theme_file_extensions[];
+      char *file2 =
+          helper_get_theme_path(config_path, rasi_theme_file_extensions, NULL);
+      char *filename = rofi_theme_parse_prepare_file(file2);
+      g_free(file2);
+      if (filename && g_file_test(filename, G_FILE_TEST_EXISTS)) {
+        if (rofi_theme_parse_file(filename)) {
+          rofi_theme_free(rofi_theme);
+          rofi_theme = NULL;
+        }
       }
+      g_free(filename);
     }
   }
   find_arg_str("-theme", &(config.theme));
@@ -1125,7 +1136,7 @@ int main(int argc, char *argv[]) {
   }
 
   if (rofi_theme == NULL || rofi_theme->num_widgets == 0) {
-    g_warning("Failed to load theme. Try to load default: ");
+    g_debug("Failed to load theme. Try to load default: ");
     rofi_theme_parse_string("@theme \"default\"");
   }
   TICK_N("Load cmd config ");
diff --git a/source/view.c b/source/view.c
index 319b6a9ee..7b488edc5 100644
--- a/source/view.c
+++ b/source/view.c
@@ -703,7 +703,7 @@ static void update_callback(textbox *t, icon *ico, unsigned int index,
     textbox_font(t, *type);
   }
 }
-static void page_changed_callback() {
+static void page_changed_callback(void) {
   rofi_view_workers_finalize();
   rofi_view_workers_initialize();
 }
diff --git a/source/widgets/widget.c b/source/widgets/widget.c
index 54f8c955f..73dfdac1e 100644
--- a/source/widgets/widget.c
+++ b/source/widgets/widget.c
@@ -250,9 +250,7 @@ void widget_draw(widget *wid, cairo_t *d) {
     cairo_restore(d);
 
     if (left != 0 || top != 0 || right != 0 || bottom != 0) {
-      // NOTE: Cairo group push/pop has same effect as cairo_save/cairo_restore,
-      // thus no need for these.
-      cairo_push_group(d);
+      cairo_save(d);
       cairo_set_operator(d, CAIRO_OPERATOR_ADD);
       cairo_translate(d, wid->x, wid->y);
       cairo_new_path(d);
@@ -409,8 +407,7 @@ void widget_draw(widget *wid, cairo_t *d) {
 
         cairo_fill(d);
       }
-      cairo_pop_group_to_source(d);
-      cairo_paint(d);
+      cairo_restore(d);
     }
   }
 }
diff --git a/source/xrmoptions.c b/source/xrmoptions.c
index f11121101..39ac90c41 100644
--- a/source/xrmoptions.c
+++ b/source/xrmoptions.c
@@ -124,7 +124,7 @@ static XrmOption xrmOptions[] = {
      NULL,
      "Whether to load and show icons",
      CONFIG_DEFAULT},
-    
+
     {xrm_String,
      "preview-cmd",
      {.str = &config.preview_cmd},
@@ -709,13 +709,14 @@ static gboolean __config_parser_set_property(XrmOption *option,
     *(option->value.num) = (p->value.b);
     option->source = (option->source & ~3) | CONFIG_FILE_THEME;
   } else if (option->type == xrm_Char) {
-    if (p->type != P_CHAR) {
-      *error = g_strdup_printf(
-          "Option: %s needs to be set with a character not a %s.", option->name,
-          PropertyTypeName[p->type]);
+
+    if (p->type != P_STRING) {
+      *error =
+          g_strdup_printf("Option: %s needs to be set with a string not a %s.",
+                          option->name, PropertyTypeName[p->type]);
       return TRUE;
     }
-    *(option->value.charc) = (p->value.c);
+    *(option->value.charc) = (p->value.s[0]);
     option->source = (option->source & ~3) | CONFIG_FILE_THEME;
   } else {
     // TODO add type
diff --git a/themes/gruvbox-dark-hard.rasi b/themes/gruvbox-dark-hard.rasi
index 10be00f05..6b4528898 100644
--- a/themes/gruvbox-dark-hard.rasi
+++ b/themes/gruvbox-dark-hard.rasi
@@ -58,5 +58,5 @@
     selected-urgent-foreground:  @urgent-foreground;
 }
 
-@import "gruvbox-common.rasinc"
+@import "gruvbox-common"
 
diff --git a/themes/gruvbox-dark-soft.rasi b/themes/gruvbox-dark-soft.rasi
index 03b120cc3..f38838521 100644
--- a/themes/gruvbox-dark-soft.rasi
+++ b/themes/gruvbox-dark-soft.rasi
@@ -58,5 +58,5 @@
     selected-urgent-foreground:  @urgent-foreground;
 }
 
-@import "gruvbox-common.rasinc"
+@import "gruvbox-common"
 
diff --git a/themes/gruvbox-dark.rasi b/themes/gruvbox-dark.rasi
index bc59022f3..1ed47e36c 100644
--- a/themes/gruvbox-dark.rasi
+++ b/themes/gruvbox-dark.rasi
@@ -58,5 +58,5 @@
     selected-urgent-foreground:  @urgent-foreground;
 }
 
-@import "gruvbox-common.rasinc"
+@import "gruvbox-common"
 
diff --git a/themes/gruvbox-light-hard.rasi b/themes/gruvbox-light-hard.rasi
index 18e51f479..fe287dbab 100644
--- a/themes/gruvbox-light-hard.rasi
+++ b/themes/gruvbox-light-hard.rasi
@@ -58,5 +58,5 @@
     selected-urgent-foreground:  @urgent-foreground;
 }
 
-@import "gruvbox-common.rasinc"
+@import "gruvbox-common"
 
diff --git a/themes/gruvbox-light-soft.rasi b/themes/gruvbox-light-soft.rasi
index f386da75e..676ccbf5d 100644
--- a/themes/gruvbox-light-soft.rasi
+++ b/themes/gruvbox-light-soft.rasi
@@ -58,5 +58,5 @@
     selected-urgent-foreground:  @urgent-foreground;
 }
 
-@import "gruvbox-common.rasinc"
+@import "gruvbox-common"
 
diff --git a/themes/gruvbox-light.rasi b/themes/gruvbox-light.rasi
index 291906830..f2845825e 100644
--- a/themes/gruvbox-light.rasi
+++ b/themes/gruvbox-light.rasi
@@ -58,5 +58,5 @@
     selected-urgent-foreground:  @urgent-foreground;
 }
 
-@import "gruvbox-common.rasinc"
+@import "gruvbox-common"