Use code block style in README

This commit is contained in:
Salt 2019-06-21 19:57:35 -05:00
parent 5d4696437d
commit f3328af31f

View File

@ -12,8 +12,10 @@ Execute `firestarter` in your `.xinitrc`, either by replacing the file or by `ex
On first run and when invoked with `firestarter -g`, Firestarter will generate a series of configuration files in `~/.config/firestarter`. These files consist of several lines that look somewhat like the following: On first run and when invoked with `firestarter -g`, Firestarter will generate a series of configuration files in `~/.config/firestarter`. These files consist of several lines that look somewhat like the following:
command -v i3 ```bash
i3 command -v i3
i3
```
Every odd line is a command that must succeed in order for the following even line to be executed. Once an even command is executed, parsing stops. When Firestarter is invoked with no arguments, every configuration file is parsed this way. Every odd line is a command that must succeed in order for the following even line to be executed. Once an even command is executed, parsing stops. When Firestarter is invoked with no arguments, every configuration file is parsed this way.
@ -21,12 +23,14 @@ This approach allows for a single file to contain very many alternatives while s
By setting a dummy execution line, one can effectively prevent an entire configuration file from being parsed in certain environments. As an example, the following configuration file will only attempt to start an X infobar in an X environment: By setting a dummy execution line, one can effectively prevent an entire configuration file from being parsed in certain environments. As an example, the following configuration file will only attempt to start an X infobar in an X environment:
[ -z "$DISPLAY" ] ```bash
: [ -z "$DISPLAY" ]
command -v polybar :
polybar bar command -v polybar
command -v lemonbar polybar bar
~/.bin/lemonbar.sh | lemonbar command -v lemonbar
~/.bin/lemonbar.sh | lemonbar
```
After all these programs have been started, firestarter executes `~/.firestarterrc` if it exists. After all these programs have been started, firestarter executes `~/.firestarterrc` if it exists.