![]() |
![]()
| ![]() |
![]()
NAMErofi-theme - Rofi theme format files Getting started with themingThe 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:
For example if we want to change the Type to filter text in the entry box we append the following:
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:
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:
Resulting in the following packing:
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.
In this example we specify the size in the em unit. Now lets change the text color of both the entry and the element-text widget to red and background to blue.
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:
We can also specify the color and width of the cursor. You could, for example, create a crimson block cursor like this:
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:
Default theme loadingBy default, rofi loads the default theme. This theme is always loaded. The default configuration contains:
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:
DescriptionThe 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 specificationEncodingThe encoding of the file is UTF-8. Both unix (\n) and windows (\r\n) newlines format are supported. But unix is preferred. CommentsC and C++ file comments are supported.
Comments can be nested and the C comments can be inline. The following is valid:
However, this is not:
White spaceWhite space and newlines, like comments, are ignored by the parser. This:
Is identical to:
File extensionThe preferred file extension for the new theme format is rasi. This is an abbreviation for rofi advanced style information. If a theme file is split over multiple files, include files can have the: rasinc extension. Basic StructureEach 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.
If there are multiple sections with the same name, they are merged. Duplicate properties are overwritten and the last parsed entry kept. Global properties sectionA 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 sectionA 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:
And is identical to:
Each section inherits the global properties. Properties can be explicitly inherited from their parent with the inherit keyword. In the following example:
The element mainbox will have the following set of properties (if mainbox is a child of window):
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 FormatThe properties in a section consist of:
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:
Some of these types are a combination of other types. String
Strings are always surrounded by double (") or single (', apostrophe) quotes. Between the quotes there can be any printable character. For example:
The string must be valid UTF-8, special characters can be escaped:
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
An integer may contain any number. For examples:
Real
A real is an integer with an optional fraction. For example:
The following is not valid: .3, 3. or scientific notation: 3.4e-3. Boolean
Boolean value is either true or false. This is case-sensitive. For example:
Imagerofi support a limited set of background-image formats.
Where the path is a string, and stop color is of type color. Colorrofi supports the color formats as specified in the CSS standard (1,2,3 and some of CSS 4)
The white-space format proposed in CSS4 is also supported. The different values are:
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:
or
Text style
Text style indicates how the highlighted text is emphasized. None indicates that no emphasis should be applied.
The following options are available on pango 1.50.0 and up:
The following option is disabled as pango crashes on this if there is eel upsizing or wrapping. This will be re-enabled once fixed:
Line style
Indicates how a line should be drawn. It currently supports:
Distance
A distance can be specified in 3 different units:
Distances used in the horizontal direction use the monitor width. Distances in the vertical direction use the monitor height. For example:
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 sizesRofi supports some maths in calculating sizes. For this it uses the CSS syntax:
It supports the following operations:
It uses the C precedence ordering. Padding
If no unit is specified, pixels are assumed. The different number of fields in the formats are parsed like:
Border
Borders are identical to padding, except that each distance field has a line style property. When no unit is specified, pixels are assumed. PositionIndicate a place on the window/monitor.
VisibilityIt is possible to hide widgets:
Reference
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:
But this is:
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:
If the property width is set globally (*{}) that value is used, if the property width is not set, the default value is used. Orientation
Specify the orientation of the widget. Cursor
Specify the type of mouse cursor that is set when the mouse pointer is over the widget. List of keywords
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
An list starts with a `[’ and ends with a ’]'. The entries in the list are comma-separated. Environment variable
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.
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.
If environment WIDTH is set, then that value is parsed, otherwise the default value (40%). Inherit
Inherits the property from its parent widget.
Elements pathsElement paths exists of two parts, the first part refers to the actual widget by name. Some widgets have an extra state. For example:
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:
Supported element pathsBase widgetsThe default widgets available in rofi and the default hierarchic:
Note that these path names match the default theme. Themes that provide a custom layout will have different elements, and structure. StateState: 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
Currently only the entrybox and scrollbar have states: Entrybox
Where visible modifier can be:
Where state is:
These can be mixed. Example:
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. ScrollbarThe 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 propertiesThe following properties are currently supported: all widgets
window
scrollbar Properties
box
textbox
listview
Listview widgetThe listview widget is special container widget. It has the following fixed children widgets:
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:
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 section. listview text highlightThe 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:
To set to red underlined:
LayoutThe 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 structureThe 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. The current layout of rofi is structured as follows:
Error message structure
Advanced layoutThe 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:
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.
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 widgetThis is a read-only textbox widget. The displayed string can be set with content. Example:
IconThis 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:
buttonThis 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).
ChildrenTo specify children, set the children property (this always happens on the box child, see example below):
The theme needs to be updated to match the hierarchy specified. Below is an example of a theme emulating dmenu:
Padding and marginJust like CSS, rofi uses the box model for each widget.
Explanation of the different parts:
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. SpacingWidgets 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).
Advanced box packingMore dynamic spacing can be achieved by adding dummy widgets, for example to make one widget centered:
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). DebuggingTo get debug information from the parser, run rofi like:
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:
To test minor changes, part of the theme can be passed on the command line, for example to set it to full-screen:
Another syntax to modify theme properties is:
To print the current theme, run:
Media supportParts of the theme can be conditionally loaded, like the CSS @media option.
It supports the following keys as constraint:
@media takes an integer number or a fraction, for integer number px can be added.
Conflicting constraintsIt 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 ParsingRofi uses pango 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:
Or
From the pango manpage: The string must have the form
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 HandlingRofi supports 3 ways of specifying 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:
Getting supported icon formats:
This uses the debug framework and prints out a list of supported image file extensions. Multiple file handlingThe 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.
Syntax:
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:
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. ExamplesSeveral 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 ALSOrofi(1), rofi-script(5), rofi-theme-selector(1)
|