1
0
Fork 0
mirror of https://github.com/polybar/polybar.git synced 2024-11-11 13:50:56 -05:00
polybar/man/lemonbuddy_config.5

126 lines
4.6 KiB
Groff
Raw Normal View History

2016-06-29 23:35:51 -04:00
.TH lemonbuddy_config 5 2016-06-22 "lemonbuddy 1.4.2" "User Configuration"
2016-06-23 04:08:14 -04:00
.SH NAME
.\" This man page will need lots of updating as documentation about lemonbuddy
.\" configuration improves.
\fBlemonbuddy_config\fR \- Configuration for a \fBlemonbuddy\fR(1) bar.
.SH SYNOPSIS
.BR $XDG_CONFIG_HOME/.config/lemonbuddy/config
.P
.BR ~/.config/lemonbuddy/config
.SH SYNTAX
.nf
2016-06-29 22:56:58 -04:00
.TP
The configuration syntax is based on the \fIini\fR file format.
.TP
A sample config section with various field types:
2016-06-23 04:08:14 -04:00
[section/name]
str = My string
2016-06-29 22:56:58 -04:00
; Quote the value to keep surrounding spaces
str = " My string"
2016-06-23 04:08:14 -04:00
bool = true
bool = on
int = 10
float = 10.0
2016-06-29 22:56:58 -04:00
.TP
Values defined in another section can be referenced using:
key = \fI${bar/top.foreground}\fR
.TP
Use BAR to target the section of the current bar:
key = \fI${BAR.foreground}\fR
.TP
Most modules define a format-N field. The formats define a set of tags. For example, the mpd module defines the following formats:
\fIformat-online\fR = ... <label-song> <icon-play> ...
\fIformat-offline\fR = the server is offline
.TP
The modules will toggle between the formats and only show the one defined for the current module state.
.TP
Each format contains the following fields:
format[-NAME]-padding = N (unit: whitespaces)
format[-NAME]-margin = N (unit: whitespaces)
format[-NAME]-spacing = N (unit: whitespaces)
format[-NAME]-offset = N (unit: pixels)
format[-NAME]-foreground = #aa[rrggbb]
format[-NAME]-background = #aa[rrggbb]
format[-NAME]-underline = #aa[rrggbb]
format[-NAME]-overline = #aa[rrggbb]
.TP
The rest of the drawtypes follow the same pattern.
2016-06-23 04:08:14 -04:00
2016-06-29 22:56:58 -04:00
.\" TODO: Describe the drawtypes
label-NAME[-(foreground|background|(under|over)line|font|padding)] = ?
icon-NAME[-(foreground|background|(under|over)line|font|padding)] = ?
ramp-NAME-[0-9]+[-(foreground|background|(under|over)line|font|padding)] = ?
animation-NAME-[0-9]+[-(foreground|background|(under|over)line|font|padding)] = ?
2016-06-23 04:08:14 -04:00
2016-06-29 22:56:58 -04:00
bar-NAME-width = N (unit: characters)
bar-NAME-format = (tokens: %fill% %indicator% %empty%)
bar-NAME-foreground-[0-9]+ = #aarrggbb
bar-NAME-indicator[-(foreground|background|(under|over)line|font|padding)] =
bar-NAME-fill[-(foreground|background|(under|over)line|font|padding)] =
bar-NAME-empty[-(foreground|background|(under|over)line|font|padding)] =
2016-06-23 04:08:14 -04:00
.fi
.SH APPLICATION SETTINGS
These settings should exist in the `settings' section within the configuration file.
.TP
\fBthrottle_limit\fR and \fBthrottle_ms\fR
Limit the amount of events sent to \fBlemonbar\fR(1) within a set timeframe. Allow at most \fIthrottle_limit\fR updates within \fIthrottle_ms\fR milliseconds.
.SH BAR SETTINGS
2016-06-29 22:56:58 -04:00
These settings should be defined in the [bar/\fIBAR\-NAME\fR] section.
2016-06-23 04:08:14 -04:00
.TP
.BR monitor
Which display to have \fBlemonbar\fR(1) exist on. You can get a list of available outputs by using the command `xrandr -q | grep " connected" | cut -d ' ' -f1'.
.TP
\fBwidth\fR, \fBheight\fR
How large the bar should be. You can specify the values as a percentage of the screen, for example `85%', or omit the `%' and give the dimension(s) in pixels.
.TP
\fBoffset_x\fR, \fBoffset_y\fR
The window offset value in pixels.
.TP
.BR bottom
If this boolean is set to `true', then \fBlemonbar\fR(1) will be instructed to render itself on the bottom of the screen.
.TP
.BR dock
If this boolean is set to `true', then require \fBlemonbar\fR(1) to dock itself.
.TP
.BR spacing
2016-06-29 22:56:58 -04:00
This integer value is used as a multiplier when adding spaces between elements.
2016-06-23 04:08:14 -04:00
.TP
.BR lineheight
How high underlines and overlines should be.
.TP
\fBbackground\fR, \fBforeground\fR, \fBlinecolor\fR
Specify the colors used by \fBlemobar\fR(1).
.TP
\fBpadding_left\fR, \fBpadding_right\fR
Specify the number of spaces to add at the start or end of the entire bar.
.TP
\fBmodule_margin_left\fR, \fBmodule_margin_right\fR
Specify the number of spaces to add before or after each module.
.TP
.BR font\-\fIid\fR
Here you can specify which fonts you wish to use. You need to set \fIid\fR to be a positive integer. The font should be specified in the following format: `\fIFONT\-NAME\fR:size=\fIFONT\-SIZE\fR;\fIOFFSET\fR'. For example, you could set `font\-0' to be `NotoSans-Regular:size=8;0'.
.TP
.BR clickareas
This value is used by \fBlemonbar\fR(1) to specify the number of clickable areas available.
.TP
.BR wm_name
2016-06-29 22:56:58 -04:00
The value to set \fIWM_NAME\fR to when running. This defaults to `lemonbuddy\-\fIBAR-NAME\fR_\fIMONITOR\fR'.
2016-06-23 04:08:14 -04:00
.TP
.BR locale
Which locale to use.
.TP
\fBmodules-left\fR, \fBmodules-center\fR, \fBmodules-right\fR
Define which modules to use in the bar.
.SH EXAMPLES
.\" TODO add examples
There are no examples yet.
.SH SEE ALSO
.TP
\fBlemonbar\fB(1), \fBlemonbuddy\fR(1)