More README polish, add nm-applet support

README.md

@@ -15,7 +15,9 @@ On first run and when invoked with `firestarter -g`, Firestarter will generate a
     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. All commands are invoked in subshells.
+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.
+
+This approach allows for a single file to contain very many alternatives while still being readable and supporting arbitrary launch requirements (such as in the case of Polybar, which requires a `launch.sh` script by default).
 
 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:
 
@@ -30,11 +32,7 @@ By setting a dummy execution line, one can effectively prevent an entire configu
 
 All STDOUT and STDERR messages from these commands are saved to a logfile in `~/.local/share/firestarter/logs` under the same name as the configuration file. By default, these logfiles are rotated every time you log in.
 
-If you set the variable `FS_NOLOG` to a nonempty value, firestarter will not keep logs and will not create a logging directory.
+If you set the variable `FS_NOLOG` to a nonempty value, firestarter will not keep logs.
-
-## Usage
-
-See `firestarter -h`
 
 ## Contribution
 

firestarter

@@ -114,6 +114,11 @@ EOF
 :
 command -v sxhkd
 sxhkd
+EOF
+	# Network daemon
+	cat << EOF > "$_configdir/network-daemon"
+command -v nm-applet
+nm-applet
 EOF
 	# Notification daemon
 	cat << EOF > "$_configdir/notification-daemon"