Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help
ROFI-THEME(5)		      File Formats Manual		 ROFI-THEME(5)

       rofi-theme - Rofi theme format files

       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.

       The  encoding  of  the file is utf-8. Both unix (\n) and	windows	(\r\n)
       newlines	format are supported. But unix is preferred.

       C and C++ file comments are supported.

       o Anything after	 // and	before a newline is considered a comment.

       o Everything between /* and */ is a comment.

       Comments	can be nested and the C	comments can be	inline.

       The following is	valid:

	      // Magic comment.
	      property:	/* comment */ value;

       However,	this is	not:

	      prop/*comment*/erty: value;

White space
       White space and newlines, like comments,	are ignored by the parser.


	      property:	name;

       Is identical to:

		   property		:


File extension
       The preferred file extension for	the new	theme format is	rasi. This  is
       an abbreviation for rofi	advanced style information.

Basic Structure
       Each  element  has a section with defined properties. Global properties
       can be defined in section * { }.	 Sub-section names begin with  a  hash
       symbol #.

       It  is  advised	to  define the global properties section on top	of the
       file to make inheritance	of properties clearer.

	      /* 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. Du-
       plicate 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 should always start with  a
       #.  Multiple elements can be specified by a ,.

       This is a valid element name:

	      element normal.normal {
		  background-color: blue;
	      button {
		  background-color: blue;

       And is identical	to:

	      element normal normal, button {
		  background-color: blue;

       Each  section inherits the global properties. Properties	can be explic-
       itly inherited from their parent	with the inherit keyword.  In the fol-
       lowing example:

	      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 main-
       box is a	child of window):

	      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:

	      {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	 prop-
       erty. The current parser	does not define	or enforce a certain type of a
       particular identifier.  When used, values with the wrong	type that can-
       not be converted	are ignored.

       The current theme format	supports different types:

       o a string

       o an integer number

       o a fractional number

       o a boolean value

       o a color

       o text style

       o line style

       o a distance

       o a padding

       o a border

       o a position

       o a reference

       o an orientation

       o a list	of keywords

       o an environment	variable

       o Inherit

       Some of these types are a combination of	other types.

String.IP +
       Format:	"[:print:]+"

       A  string is always surrounded by double	quotes ("). Between the	quotes
       there can be any	printable character.

       For example:

	      font: "Awasome 12";

       The string must be valid	UTF-8.

Integer.IP +
       Format: [-+]?[:digit:]+

       An integer may contain any number.

       For examples:

	      lines: 12;

Real.IP	+
       Format: [-+]?[:digit:]+(\.[:digit:]+)?

       A real is an integer with an optional fraction.

       For example:

	      real: 3.4;

       The following is	not valid: .3, 3. or scientific	notation: 3.4e-3.

Boolean.IP +
       Format: (true|false)

       Boolean value is	either true or false. This is case-sensitive.

       For example:

	      dynamic: false;

       rofi supports the color formats as specified in the CSS standard	(1,2,3
       and some	of CSS 4)

       o Format: #{HEX}{3} (rgb)

       o Format: #{HEX}{4} (rgba)

       o Format: #{HEX}{6} (rrggbb)

       o Format: #{HEX}{8} (rrggbbaa)

       o Format: rgb[a]({INTEGER},{INTEGER},{INTEGER}[,	{PERCENTAGE}])

       o Format: rgb[a]({INTEGER}%,{INTEGER}%,{INTEGER}%[, {PERCENTAGE}])

       o Format: hsl[a]( {ANGLE}, {PERCENTAGE},	{PERCENTAGE} [,	{PERCENTAGE}])

       o Format: hwb[a]( {ANGLE}, {PERCENTAGE},	{PERCENTAGE} [,	{PERCENTAGE}])

	 [, {PERCENTAGE} ])

       o Format: {named-color} [ / {PERCENTAGE}	]

       The white-space format proposed in CSS4 is also supported.

       The different values are:

       o {HEX} is a hexadecimal	number ('0-9a-f' case insensitive).

       o {INTEGER} value can be	between	0 and 255 or 0-100  when  representing

       o {ANGLE}  is the angle on the color wheel, can be in deg, rad, grad or
	 turn. When no unit is specified, degrees is assumed.

       o {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, Char-
       treuse, Chocolate,  Coral,  CornflowerBlue,  Cornsilk,  Crimson,	 Cyan,
       DarkBlue, DarkCyan, DarkGoldenRod, DarkGray, DarkGrey, DarkGreen, Dark-
       Khaki, 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, LightGolden-
       RodYellow,  LightGray,  LightGrey,  LightGreen, LightPink, LightSalmon,
       LightSeaGreen,  LightSkyBlue,  LightSlateGray,  LightSlateGrey,	Light-
       SteelBlue, LightYellow, Lime, LimeGreen,	Linen, Magenta,	Maroon,	Mediu-
       mAquaMarine, MediumBlue,	 MediumOrchid,	MediumPurple,  MediumSeaGreen,
       MediumSlateBlue,	 MediumSpringGreen,  MediumTurquoise, MediumVioletRed,
       MidnightBlue, MintCream,	MistyRose, Moccasin, NavajoWhite,  Navy,  Old-
       Lace, Olive, OliveDrab, Orange, OrangeRed, Orchid, PaleGoldenRod, Pale-
       Green, 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:

	      background-color:	#FF0000;
	      border-color: rgba(0,0,1,	0.5);
	      text-color: SeaGreen;


	      background-color:	transparent;
	      text-color: Black;

Text style.IP +
       Format: (bold|italic|underline|strikethrough|none)

       Text style indicates how	the highlighted	text is	emphasized. None indi-
       cates that no emphasis should be	applied.

       o bold: make the	text thicker then the surrounding text.

       o italic: put the highlighted text in script type (slanted).

       o underline: put	a line under the highlighted text.

       o strikethrough:	put a line through the highlighted text.

       o small caps: emphasise the text	using capitalization.

	      For some reason small caps does not work on some systems.

Line style.IP +
       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.IP +
       Format: {Integer}px

       o Format: {Real}em

       o Format: {Real}ch

       o Format: {Real}%

       o Format: {Integer}mm

       A distance can be specified in 3	different units:

       o px: Screen pixels.

       o em: Relative to text height.

       o ch: Relative to width of a single number.

       o mm: Actual size in millimeters	(based on dpi).

       o %:  Percentage	of the monitor size.

       Distances used in the horizontal	direction use the monitor width.  Dis-
       tances in the vertical direction	use the	monitor	height.	 For example:

		 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

	      width: calc( 100%	- 37px );

       It supports the following operations:

       o +   : Add

       o -   : Subtract

       o /   : Divide

       o *   : Multiply

       o %   : Multiply

       o min : Minimum of l or rvalue;

       o max : Maximum of l or rvalue;

       It uses the C precedence	ordering.

Padding.IP +
       Format: {Integer}

       o Format: {Distance}

       o Format: {Distance} {Distance}

       o Format: {Distance} {Distance} {Distance}

       o Format: {Distance} {Distance} {Distance} {Distance}

       If no unit is specified,	pixels are assumed.

       The different number of fields in the formats are parsed	like:

       o 1 field: all

       o 2 fields: topbottom leftright

       o 3 fields: top,	leftright, bottom

       o 4 fields: top,	right, bottom, left

Border.IP +
       Format: {Integer}

       o Format: {Distance}

       o Format: {Distance} {Distance}

       o Format: {Distance} {Distance} {Distance}

       o Format: {Distance} {Distance} {Distance} {Distance}

       o Format: {Distance} {Line style}

       o Format: {Distance} {Line style} {Distance} {Line style}

       o Format:  {Distance}  {Line  style} {Distance} {Line style} {Distance}
	 {Line style}

       o 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.

       Indicate	a place	on the window/monitor.

       o Format:  (center|east|north|west|south|north  east|north   west|south
	 west|south east)

	      north west   |	north	 |  north east
		    west   |   center	 |  east
	      south west   |	south	 |  south east

       It is possible to hide widgets:

       inputbar	{
	   enabled: false; }

Reference.IP +
       Format: @{PROPERTY NAME}

       A reference can point to	another	reference. Currently, the maximum num-
       ber 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:

	      highlight: bold @pink;

       But this	is:

	      *	{
		  myhigh: bold #FAA;

	      window {
		  highlight: @myhigh;

Orientation.IP +
       Format: (horizontal|vertical)

       Specify the orientation of the widget.

List of	keywords.IP +
       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.

Environment variable.IP	+
       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.

	      *	{
		  background-color: ${BG};

Inherit.IP +
       Format: inherit

       Inherits	the property from its parent widget.

	      mainbox {
		  border-color:	inherit;

       Element	paths exists of	two parts, the first part refers to the	actual
       widget by name.	Some widgets have an extra state.

       For example:

	      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:

	      element .selected	{

	      element.selected {
	      element selected {

       The current widgets available in	rofi:

       o window

       o overlay: the overlay widget.

       o mainbox: The mainbox box.

       o inputbar: The input bar box.

       o box: the horizontal @box packing the widgets

       o case-indicator: the case/sort indicator @textbox

       o prompt: the prompt @textbox

       o entry:	the main entry @textbox

       o num-rows: Shows the total number of rows.

       o num-filtered-rows: Shows the total number of rows after filtering.

       o listview: The listview.

       o scrollbar: the	listview scrollbar

       o element: a box	in the listview	holding	the entries

       o element-icon: the widget in the listview's  entry  showing  the  (op-
	 tional) icon

       o element-index:	 the  widget in	the listview's entry keybindable index

       o element-text: the widget in the listview's entry showing the text.

       o mode-switcher:	the main horizontal @box packing the buttons.

       o button: the buttons @textbox for each mode

       o message: The container	holding	the textbox.

       o 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 of widget

       Optional	flag(s)	indicating state of the	widget,	used for theming.

       These are appended after	the name or class of the widget.

       button selected.normal {	}

       element selected.urgent { }

       Currently only the entrybox and scrollbar have states:

       {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.


	      nametotextbox {
		  background-color: #003642;
		  text-color: #008ed4;

       Sets  all  selected textboxes marked active to the given	text and back-
       ground color.  Note that	a state	 modifies  the	original  element,  it
       therefore contains all the properties of	that element.

       The  scrollbar  uses  the handle	state when drawing the small scrollbar
       handle.	This allows the	colors used for	drawing	the handle to  be  set

       The following properties	are currently supported:

   all widgets:.IP +o 2
       enabled:		enable/disable the widget

       o padding:	  padding Padding on the inside	of the widget

       o margin:	  padding Margin on the	outside	of the widget

       o border:	  border Border	around the widget (between padding and

       o border-radius:	   padding Sets	a radius on the	corners	 of  the  bor-

       o background-color:	color Background color

       o border-color:	    color Color	of the border

   window:.IP +o	2
       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, al-
       lowing you to push the window left/right/up/down

   scrollbar:.IP +o 2
       background-color:    color

       o handle-width:	      distance

       o handle-color:	      color

       o border-color:	      color

   box:.IP +o 2
       orientation:	 orientation
	   Set the direction the elements are packed.

       o spacing:	  distance
	     Distance between the packed elements.

   textbox:.IP +o 2
       background-color:  color

       o border-color:	    the	color used for the border around the widget.

       o font:		    the	font used by this textbox (string).

       o str:		    the	string to display by this textbox (string).

       o vertical-align:    vertical alignment of the text (0 top, 1 bottom).

       o horizontal-align:  horizontal	alignment  of  the  text  (0  left,  1

       o text-color:	    the	text color to use.

       o highlight:	     text  style {color}.  color is optional, multiple
	 highlight styles can be added like: bold underline italic #000000;

       o width:		    override the desired width for the textbox.

       o content:	    Set	the displayed text (String).

       o placeholder:	    Set	the displayed text (String)  when  nothing  is

       o placeholder-color: Color of the placeholder text.

       o blink:		    Enable/Disable blinking on an input	textbox	(Bool-

   listview:.IP	+o 2
       columns:		integer	Number of columns to show (at least 1)

       o fixed-height:	  boolean Always show lines rows, even if  fewer  ele-
	 ments are available.

       o dynamic:	   boolean True	if the size should change when filter-
	 ing the list, False if	it should keep the original height.

       o scrollbar:	  boolean If the scrollbar should be enabled/disabled.

       o scrollbar-width: distance Width of the	scrollbar

       o cycle:		  boolean When navigating, it should wrap around

       o spacing:	  distance Spacing between the elements	(both vertical
	 and horizontal)

       o lines:		  integer Number of rows to show in the	list view.

       o layout:	   orientation Indicate	how elements are stacked. Hor-
	 izontal implements the	dmenu style.

       o reverse:	  boolean Reverse the ordering	(top  down  to	bottom

       o fixed-columns:	    boolean  Do	not reduce the number of columns shown
	 when number of	visible	elements is not	enough to fill them all.

       Each element is a box called element. Each element can contain an  ele-
       ment-icon and element-text.

   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 prop-
       erty is used) to	change the style of highlighting.  The highlight prop-
       erty consist of the text-style property and a color.

       To disable highlighting:

		element-text {
		  highlight: None;

       To set to red underlined:

		element-text {
		  highlight: underline red;

       The new format allows the layout	of the rofi window to be  tweaked  ex-
       tensively.   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 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

       The current layout of rofi is structured	as follows:

	      |	window {BOX:vertical}								   |
	      |	|-------------------------------------------------------------------------------|  |
	      |	| mainbox  {BOX:vertical}							|  |
	      |	| |---------------------------------------------------------------------------|	|  |
	      |	| | inputbar {BOX:horizontal}						      |	|  |
	      |	| | |---------|	|-----------------------------------------------------|	|---| |	|  |
	      |	| | | prompt  |	| entry						      |	|ci | |	|  |
	      |	| | |---------|	|-----------------------------------------------------|	|---| |	|  |
	      |	| |---------------------------------------------------------------------------|	|  |
	      |	|										|  |
	      |	| |---------------------------------------------------------------------------|	|  |
	      |	| | message								      |	|  |
	      |	| | |-----------------------------------------------------------------------| |	|  |
	      |	| | | textbox								    | |	|  |
	      |	| | |-----------------------------------------------------------------------| |	|  |
	      |	| |---------------------------------------------------------------------------|	|  |
	      |	|										|  |
	      |	| |-----------------------------------------------------------------------------|  |
	      |	| | listview									|  |
	      |	| |-----------------------------------------------------------------------------|  |
	      |	|										|  |
	      |	| |---------------------------------------------------------------------------|	|  |
	      |	| |  mode-switcher {BOX:horizontal}					      |	|  |
	      |	| | |---------------|	|---------------|  |--------------| |---------------| |	|  |
	      |	| | | Button	    |	| Button	|  | Button	  | | Button	    | |	|  |
	      |	| | |---------------|	|---------------|  |--------------| |---------------| |	|  |
	      |	| |---------------------------------------------------------------------------|	|  |
	      |	|-------------------------------------------------------------------------------|  |

	      ci is the	case-indicator

   Error message structure
	      |	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  functional-

       o prompt

       o entry

       o overlay

       o case-indicator

       o message

       o listview

       o mode-switcher

       o num-rows

       o 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.

       o mainbox Packs:	inputbar, message, listview, mode-switcher

       o 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:

       o textbox:  This	 is  a textbox widget. The displayed string can	be set
	 with str.

       o icon: This is an icon widget. The displayed  icon  can	 be  set  with
	 filename and size with	size.

       o button:  This is a textbox widget that	can have a 'clickable' action.
	 The action can	be set to: ok accept entry.  custom accept custom  in-
	 put.  ok|alternate: accept entry and launch alternate action (for run
	 launch	in  terminal).	 custom|alternate:  accept  custom  input  and
	 launch	alternate action.

       To  specify children, set the children property (this always happens on
       the box child, see example below):

	      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:

	      *	{
		  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.

	      |	margin								  |
	      |	 |-------------------------------------------------------------|  |
	      |	 | border						       |  |
	      |	 | |---------------------------------------------------------| |  |
	      |	 | | padding						     | |  |
	      |	 | | |-----------------------------------------------------| | |  |
	      |	 | | | content						   | | |  |
	      |	 | | |-----------------------------------------------------| | |  |
	      |	 | |---------------------------------------------------------| |  |
	      |	 |-------------------------------------------------------------|  |

       Explanation of the different parts:

       o Content - The content of the widget.

       o Padding - Clears an area around the widget.  The  padding  shows  the
	 background color of the widget.

       o Border	- A border that	goes around the	padding	and content.  The bor-
	 der use the border-color of the widget.

       o Margin	- Clears an area outside the border.  The margin is  transpar-

       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  bor-
       der, a linestyle	and radius can be set.

       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).

	      |	 |--------| 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 exam-
       ple to make one widget centered:

	      |	 |-----------|	|--------|  |-----------|  |
	      |	 | dummy     |	| child	 |  | dummy	|  |
	      |	 | expand: y |	|	 |  | expand: y	|  |
	      |	 |	     |	|	 |  |		|  |
	      |	 |	     |	|	 |  |		|  |
	      |	 |	     |	|	 |  |		|  |
	      |	 |-----------|	|--------|  |-----------|  |

       If both dummy widgets are set to	expand,	child will  be	centered.  De-
       pending 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).

       To get debug information	from the parser, run rofi like:

	      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:

	      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:

	      rofi -theme-str '#window { fullscreen:true;}' -show run

       To print	the current theme, run:

	      rofi -dump-theme

Media support
       Parts of	the theme can be conditionally loaded, like the	CSS @media op-

	      @media ( min-width: 120 )	{


       It supports the following keys as constraint:

       o min-width:	    load when width is bigger or equal then value.

       o max-width:	    load when width is smaller then value.

       o min-height:	    load when height is	bigger or equal	then value.

       o max-height:	    load when height is	smaller	then value.

       o min-aspect-ratio   load when aspect ratio is over value.

       o max-aspect-ratio:  load when aspect ratio is under value.

       o monitor-id:	    The	monitor	id, see	rofi -help for id's.

       @media takes an integer number or a fraction, for integer number	px can
       be added.

	      @media ( min-width: 120 px ) {


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

       o import:  Import and parse a second file.

       o theme:	  Discard theme, and load file as a fresh theme.


	      @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

       o ${XDG_CONFIG_HOME}/rofi/themes/

       o ${XDG_CONFIG_HOME}/rofi/

       o ${XDG_DATA_HOME}/rofi/themes/

       o ${INSTALL PREFIX}/share/rofi/themes/

       A name is resolved as a filename	by appending the .rasi extension.

       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:

       rofi(1),	rofi-script(5),	rofi-theme-selector(1)

				  rofi-theme			 ROFI-THEME(5)

NAME | DESCRIPTION | FORMAT SPECIFICATION | Encoding | Comments | White space | File extension | Basic Structure | Global properties section | Element theme section | Properties Format | String.IP + | Integer.IP + | Real.IP + | Boolean.IP + | Color | Text style.IP + | Line style.IP + | Distance.IP + | Padding.IP + | Border.IP + | Position | Visibility | Reference.IP + | Orientation.IP + | List of keywords.IP + | Environment variable.IP + | Inherit.IP + | ELEMENTS PATHS | SUPPORTED ELEMENT PATH | Name | State | SUPPORTED PROPERTIES | Layout | DEBUGGING | Media support | Multiple file handling | EXAMPLES | SEE ALSO

Want to link to this manual page? Use this URL:

home | help