README.rst: Setting proper pygments for code blocks. Fixing broken new line.

1 files changed, 11 insertions, 7 deletions

diff --git a/README.rst b/README.rst
index bbf1ada..2e1a1ec 100644
--- a/README.rst
+++ b/README.rst
@@ -13,9 +13,9 @@ Separate tmux environments
 | Here it is used for a couple of services to start an environment in which other |cli| programs can run.
 | In those services the following |systemd.exec| is set:
 
-    .. code:: systemd
+  .. code:: ini
 
-      Environment=TMUX_TMPDIR=%t/tmux
+    Environment=TMUX_TMPDIR=%t/tmux
 
 | This will store the |tmux| server socket in the users' *XDG_RUNTIME_DIR*. Therefore it will be necessary to set your *TMUX_TMPDIR* |environment_variable| for your |bash| or |zsh| (or whatever you run) to the following:
 
@@ -49,14 +49,14 @@ compton --user
 ______________
 | The |compton| user service needs a properly exported *$DISPLAY* variable to work. You can set this in your |systemd-user.conf|:
 
-  .. code:: systemd
+  .. code:: ini
 
     DefaultEnvironment=DISPLAY=:0
 
 | The compton user service is anti-dependent on the `REALTIME kernel parameter` (i.e. it will not start, when booting into a kernel with that option set).
 | You can start and enable it like any other systemd user service:  
 
-  .. code:: systemd
+  .. code:: bash
 
      systemctl --user start compton
      systemctl --user enable compton
@@ -72,7 +72,7 @@ ___________
 | The *cpupower-rt.service* is dependant on the `REALTIME kernel parameter`. It will only start, if that condition is met.  
 | You can start and enable it like any other systemd service:
 
-  .. code:: systemd
+  .. code:: bash
 
     systemctl start cpupower-rt
     systemctl enable cpupower-rt
@@ -82,7 +82,7 @@ ____________
 | The systemd user service *irssi.service* starts the |irc| client |irssi| in a separate |tmux| environment for the current user.
 | To connect to it after starting the service, just do
 
-  .. code:: systemd
+  .. code:: bash
 
     tmux -L irssi attach
 
@@ -91,6 +91,8 @@ ____________
 JACK2 comes with a dbus interface. Unfortunately systemd's efforts regarding [kdbus](https://en.wikipedia.org/wiki/Kdbus) and integrating kernel CPU [cgroups](https://www.kernel.org/doc/Documentation/cgroups/) (and thereby also real-time scheduling) is still somewhat in limbo.  
 The included jack@.service starts JACK using */usr/bin/jackd"* (so no dbus), according to a profile. The name of that profile follows after the *@* on starting/ activating the unit and must be found in either `/etc/jack/` or `~/.config/jack/`.  
 
+  .. code:: bash
+
     systemctl --user start jack@fw1
     systemctl --user enable jack@fw1
 
@@ -102,7 +104,7 @@ _________________
 | Currently it starts |htop|, |glances| and asks loginctl for the current user processes in a `separate |tmux| environment`.
 | To connect to it after starting the service, just do  
 
-  .. code:: systemd
+  .. code:: bash
 
     tmux -L mon attach
 
@@ -216,12 +218,14 @@ ______________
 
     systemctl --user start weechat
     systemctl --user enable weechat
+
 | To connect to it after starting the service, just do
 
   .. code:: bash
 
     tmux -L weechat attach
 
+
 .. |systemd| raw:: html
 
   <a href="https://en.wikipedia.org/wiki/Systemd" target="_blank">systemd</a>