diff --git a/configure.ac b/configure.ac
index c8565ad2f..e6e4d26a4 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,4 +1,4 @@
-AC_INIT([rofi], [1.7.7-dev], [https://github.com/davatorium/rofi/],[],[https://github.com/davatorium/rofi/discussions])
+AC_INIT([rofi], [1.7.8], [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/meson.build b/meson.build
index 57a5c9708..1dea4fb86 100644
--- a/meson.build
+++ b/meson.build
@@ -1,5 +1,5 @@
 project('rofi', 'c',
-    version: '1.7.7-dev',
+    version: '1.7.8',
     meson_version: '>=0.59.0',
     license: [ 'MIT' ],
     default_options: [
diff --git a/mkdocs/docs/1.7.8/rofi-debugging.5.markdown b/mkdocs/docs/1.7.8/rofi-debugging.5.markdown
new file mode 100644
index 000000000..4df15d529
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi-dmenu.5.markdown b/mkdocs/docs/1.7.8/rofi-dmenu.5.markdown
new file mode 100644
index 000000000..27e484b3f
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi-keys.5.markdown b/mkdocs/docs/1.7.8/rofi-keys.5.markdown
new file mode 100644
index 000000000..8aeefacc2
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi-script.5.markdown b/mkdocs/docs/1.7.8/rofi-script.5.markdown
new file mode 100644
index 000000000..aeeac8fda
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi-sensible-terminal.1.markdown b/mkdocs/docs/1.7.8/rofi-sensible-terminal.1.markdown
new file mode 100644
index 000000000..1406299dd
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi-theme-selector.1.markdown b/mkdocs/docs/1.7.8/rofi-theme-selector.1.markdown
new file mode 100644
index 000000000..1fa8b6fe7
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi-theme.5.markdown b/mkdocs/docs/1.7.8/rofi-theme.5.markdown
new file mode 100644
index 000000000..dd6c2b4f1
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi-thumbnails.5.markdown b/mkdocs/docs/1.7.8/rofi-thumbnails.5.markdown
new file mode 100644
index 000000000..e18ced7e1
--- /dev/null
+++ b/mkdocs/docs/1.7.8/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.8/rofi.1.markdown b/mkdocs/docs/1.7.8/rofi.1.markdown
new file mode 100644
index 000000000..79f342b88
--- /dev/null
+++ b/mkdocs/docs/1.7.8/rofi.1.markdown
@@ -0,0 +1,1188 @@
+# 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;
+      /** Disable DBusActivatable */
+      DBusActivatable: 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/mkdocs.yml b/mkdocs/mkdocs.yml
index 7ebe364e2..e90154d98 100644
--- a/mkdocs/mkdocs.yml
+++ b/mkdocs/mkdocs.yml
@@ -23,6 +23,14 @@ nav:
     - Debugging: current/rofi-debugging.5.markdown
     - Keys: current/rofi-keys.5.markdown
     - Thumbnails: current/rofi-thumbnails.5.markdown
+  - 1.7.8:
+    - Rofi: 1.7.8/rofi.1.markdown 
+    - Themes: 1.7.8/rofi-theme.5.markdown
+    - Dmenu: 1.7.8/rofi-dmenu.5.markdown
+    - Script: 1.7.8/rofi-script.5.markdown
+    - Debugging: 1.7.8/rofi-debugging.5.markdown
+    - Keys: 1.7.8/rofi-keys.5.markdown
+    - Thumbnails: 1.7.8/rofi-thumbnails.5.markdown
   - 1.7.7:
     - Rofi: 1.7.7/rofi.1.markdown 
     - Themes: 1.7.7/rofi-theme.5.markdown