manpage: use pandoc instead of ruby-ronn

reasonning: ruby-ronn is abandonned, and will most likely be dropped
from debian and ubuntu [1]

1: https://bugs.debian.org/796497

Thanks to @quinnuendo for the edits on the markdown file!

Closes vivien#186

Makefile

@@ -48,8 +48,8 @@ $(PROGRAM): ${OBJS}
 
 man: $(PROGRAM).1
 
-$(PROGRAM).1: $(PROGRAM).1.ronn
-	ronn -w -r $<
+$(PROGRAM).1: $(PROGRAM).1.md
+	pandoc --to man --standalone --output $@ $<
 
 clean:
 	rm -f src/*.o $(PROGRAM)

README.md

@@ -87,8 +87,8 @@ Or you may install i3blocks from source:
     $ make clean debug # or make clean all
     # make install
 
-Note: the generation of the manpage requires the `ronn` utility, packaged in
-common distributions as `ruby-ronn`.
+Note: the generation of the manpage requires the `pandoc` utility, packaged in
+common distributions as `pandoc`.
 
 ### Usage
 

i3blocks.1.ronn → i3blocks.1.md

@@ -1,20 +1,21 @@
-i3blocks(1) -- A flexible scheduler for i3bar
-=============================================
+% I3BLOCKS(1)
 
-## SYNOPSIS
+# NAME
+i3blocks - A flexible scheduler for your i3bar blocks
 
-`i3blocks` [-c <configfile>] [-v]... [-h] [-V]
+# SYNOPSIS
 
-## DESCRIPTION
+i3blocks [*options*]
+
+# DESCRIPTION
 
 **i3blocks** allows one to easily describe blocks in a simple format, and
 generate a status line for i3bar(1). It handles clicks, signals and time
 interval for user scripts.
 
-## OPTIONS
-
-  * `-c` <configfile>:
-    Specifies an alternate configuration file path. By default, i3blocks looks 
+#OPTIONS
+-c <configfile>
+:   Specifies an alternate configuration file path. By default, i3blocks looks 
     for configuration files in the following order (note that /etc may be
     prefixed with /usr/local depending on the compilation flags):
 
@@ -23,18 +24,18 @@ interval for user scripts.
         3. /etc/xdg/i3blocks/config (or $XDG_CONFIG_DIRS/i3blocks/config if set)
         4. /etc/i3blocks.conf
 
-  * `-v`:
-    Log level. This option is cumulative. By default, error messages are
+-v
+:   Log level. This option is cumulative. By default, error messages are
     displayed on stderr. Passed once, a failure during an update is shown
     within the block. Passed twice enables the debug messages on stderr.
 
-  * `-V`:
-    Print the version and exit.
+-V
+:   Print the version and exit.
 
-  * `-h`:
-    Print the help message and exit.
+-h
+:   Print the help message and exit.
 
-## CONFIGURATION
+# CONFIGURATION
 
 The configuration file is an ini file. Each section describes a new block.
 A line beginning with a `#` sign is a comment, and empty lines are ignored.
@@ -62,72 +63,85 @@ To use i3blocks as your status line, define it in a *bar* block of your
       status_command i3blocks
     }
 
-## BLOCK
+# BLOCK
 
-The properties used to describe a block are the keys specified in the [i3bar
-protocol](http://i3wm.org/docs/i3bar-protocol.html), plus additional properties
+The properties used to describe a block are the keys specified in the i3bar
+protocol http://i3wm.org/docs/i3bar-protocol.html , plus additional properties
 used by **i3blocks** to describe when and how to update a block.
 All the supported properties are described below.
 
 The following keys are standard, see
-[http://i3wm.org/docs/i3bar-protocol.html](http://i3wm.org/docs/i3bar-protocol.html)
+http://i3wm.org/docs/i3bar-protocol.html
 for details.
 
-  * `full_text`
-  * `short_text`
-  * `color`
-  * `min_width`
-  * `align`
-  * `name`
-  * `instance`
-  * `urgent`
-  * `separator`
-  * `separator_block_width`
-  * `markup`
+ - `full_text`
+
+ - `short_text`
+
+ - `color`
+
+ - `min_width`
+
+ - `align`
+
+ - `name`
+
+ - `instance`
+
+ - `urgent`
+
+ - `separator`
+
+ - `separator_block_width`
+
+ - `markup`
 
 The following keys are specific to **i3blocks**.
 
-  * `command`:
-	The command executed by a shell, used to update the block. The expected
-    behavior is described below, in the [COMMAND][] section.
-
-  * `interval`:
-    If it is a positive integer, then the block is spawned on startup and the
-    value is used as a time interval in seconds to schedule future updates.
-    If unspecified or 0, the block won't be executed on startup (which is
-    useful to simulate buttons).
-    If "once" (or -1), the block will be executed only on startup (note that a
-    click or signal will still trigger an update).
-    If "repeat" (or -2), the block will be spawned on startup, and as soon as
-    it terminates (useful to repeat blocking commands). Use with caution!
-    If "persist" (or -3), the block will be executed only on startup, and
-    updated as soon as it outputs a line. Thus limited to single line updates.
-
-  * `signal`:
-	The signal number used to update the block. All the real-time (think
-    prioritized and queueable) signals are available to the user. The number is
-    valid between 1 and N, where SIGRTMIN+N = SIGRTMAX. (Note: there are 31
-    real-time signals in Linux.) For instance, `signal=10` means that this
-    block will be updated when **i3blocks** receives SIGRTMIN+10.
-
-  * `label`:
-	An optional label to preprend to the `full_text` after an update.
-
-  * `format`:
-    This property specifies the format of the output text. The default format
-    is plain text, as described in the [COMMAND][] section.
-    If "json" (or 1) is used, the block output is parsed as JSON.
-
-## COMMAND
+`command`
+:	 The command executed by a shell, used to update the block. The expected
+	 behavior is described below, in the **COMMAND** section.
+
+`interval`
+:    If it is a positive integer, then the block is spawned on startup and the
+	 value is used as a time interval in seconds to schedule future updates.
+	 If unspecified or 0, the block won't be executed on startup (which is
+	 useful to simulate buttons).
+
+	 If "*once*" (or -1), the block will be executed only on startup (note that a
+	 click or signal will still trigger an update).
+
+	 If "*repeat*" (or -2), the block will be spawned on startup, and as soon as
+	 it terminates (useful to repeat blocking commands). Use with caution!
+
+	 If "*persist*" (or -3), the block will be executed only on startup, and
+	 updated as soon as it outputs a line. Thus limited to single line updates.
+
+`signal`
+:	 The signal number used to update the block. All the real-time (think
+     prioritized and queueable) signals are available to the user. The number is
+     valid between 1 and N, where SIGRTMIN+N = SIGRTMAX. (Note: there are 31
+     real-time signals in Linux.) For instance, `signal=10` means that this
+     block will be updated when **i3blocks** receives SIGRTMIN+10.
+
+`label`
+: 	An optional label to preprend to the `full_text` after an update.
+
+`format`
+:    This property specifies the format of the output text. The default format
+     is plain text, as described in the **COMMAND** section.
+     If "json" (or 1) is used, the block output is parsed as JSON.
+
+# COMMAND
 
 The value of the `command` key will be passed and executed as is by a shell.
 
 The standard output of the command line is used to update the block content.
 Each non-empty line of the output will overwrite the corresponding property:
 
-  1. full_text
-  2. short_text
-  3. color
+1. full_text
+2. short_text
+3. color
 
 For example, this script sets the `full_text` in blue but no `short_text`:
 
@@ -143,28 +157,24 @@ For example, this script prints the battery percentage and sets the urgent flag
 if it is below 10%:
 
     BAT=`acpi -b | grep -E -o '[0-9][0-9]?%'`
-
     echo "BAT: $BAT"
     test ${BAT%?} -le 10 && exit 33 || exit 0
 
 When forking a block command, **i3blocks** will set the environment with some 
 `BLOCK_*` variables. The following variables are always provided, with
 eventually an empty string as the value.
 
-  * `BLOCK_NAME`:
-    The name of the block (usually the section name).
-
-  * `BLOCK_INSTANCE`:
-    An optional argument to the script.
+`BLOCK_NAME`
+:   The name of the block (usually the section name).
 
-  * `BLOCK_INTERVAL`:
-    The interval that the block is set to update with (see `interval` above).
+`BLOCK_INSTANCE`
+:   An optional argument to the script.
 
-  * `BLOCK_BUTTON`:
-    Mouse button (1, 2 or 3) if the block was clicked.
+`BLOCK_BUTTON`
+:   Mouse button (1, 2 or 3) if the block was clicked.
 
-  * `BLOCK_X` and `BLOCK_Y`:
-	Coordinates where the click occurred, if the block was clicked.
+`BLOCK_X` and `BLOCK_Y`
+:   Coordinates where the click occurred, if the block was clicked.
 
 Here is an example using the environment:
 
@@ -181,7 +191,7 @@ Here is an example using the environment:
 Note that **i3blocks** provides a set of optional scripts for convenience, such
 as network status, battery check, cpu load, volume, etc.
 
-## EXAMPLES
+# EXAMPLES
 
 As an example, here is a close configuration to i3status(1) default settings:
 
@@ -231,31 +241,31 @@ scripts under `~/bin/blocks/` with the same name as the blocks:
     [cpu]
     [datetime]
 
-## SEE ALSO
+# SEE ALSO
 
 The development of i3blocks takes place on [Github](https://github.com/vivien/i3blocks).
+
 The [wiki](https://github.com/vivien/i3blocks/wiki) is a good
 source of examples for blocks and screenshots.
 
-i3(1), i3bar(1), i3status(1)
-
-## BUGS
+`i3` (1), `i3bar` (1), `i3status` (1)
 
-### Reporting Bugs
+# Reporting Bugs
 
 Please report bugs on the [issue tracker](https://github.com/vivien/i3blocks/issues).
 
-### Known Bugs
+# Known Bugs
 
 None.
 
-## AUTHOR
+# AUTHOR
 
 Written by Vivien Didelot <vivien.didelot@gmail.com>.
 
-## COPYRIGHT
+# COPYRIGHT
 
 Copyright (C) 2014 Vivien Didelot <vivien.didelot@gmail.com>
+
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
 
 This is free software: you are free to change and redistribute it. There is NO