From f3328af31fe5b79840ee419a75a572ed41bfa1a4 Mon Sep 17 00:00:00 2001 From: Salt Date: Fri, 21 Jun 2019 19:57:35 -0500 Subject: [PATCH] Use code block style in README --- README.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index f614acb..20d3394 100644 --- a/README.md +++ b/README.md @@ -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: - command -v i3 - i3 +```bash +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. @@ -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: - [ -z "$DISPLAY" ] - : - command -v polybar - polybar bar - command -v lemonbar - ~/.bin/lemonbar.sh | lemonbar +```bash +[ -z "$DISPLAY" ] +: +command -v polybar +polybar bar +command -v lemonbar +~/.bin/lemonbar.sh | lemonbar +``` After all these programs have been started, firestarter executes `~/.firestarterrc` if it exists.