From 6c761dcb9610fba4d2d73c9352f659604a0981f8 Mon Sep 17 00:00:00 2001
From: o0nd7ots <124466962+o0nd7ots@users.noreply.github.com>
Date: Mon, 18 Mar 2024 11:46:48 +0000
Subject: [PATCH 1/3] Readme: Improved support

I have extracted "Multiple notification daemons" to another section.

Also I have added a line explaining that mako needs a session bus.

Later I have split systemd and non-systemd systems into two paragraphs
---
 README.md | 21 +++++++++++----------
 1 file changed, 11 insertions(+), 10 deletions(-)

diff --git a/README.md b/README.md
index e3a4a37..08545b6 100644
--- a/README.md
+++ b/README.md
@@ -12,19 +12,20 @@ Feel free to join the IRC channel: #emersion on irc.libera.chat.
 
 ## Running
 
+`mako` requires an active session bus to function properly. 
 
-`mako` will run automatically when a notification is emitted. This happens via
-D-Bus activation, so you don't really need to explicitly start it up (this also
-allows delaying its startup time and speed up system startup).
+If you are using SystemD `mako` will run automatically when a notification is emitted.
+This happens via D-Bus activation, so you don't really need to explicitly 
+start it up (this also allows delaying its startup time and speed up system startup).
 
-If you have several notification daemons installed though, you might want to
-explicitly start this one. Some ways of achieving this is:
-
-- If you're using Sway you can start mako on launch by putting `exec mako` in
-  your configuration file.
+If you are not using systemd, you might need to manually start a dbus user session
+with the compositor of your choice from the display manager. The command run should
+look something like this: `dbus-launch --exit-with-session COMPOSITOR`.
 
-- If you are not using systemd, you might need to manually start a dbus user
-  session: `dbus-daemon --session --address=unix:path=$XDG_RUNTIME_DIR/bus`
+### Multiple notification daemons
+If you have several notification daemons installed though, you might want to
+explicitly start this one.
+This is usually done by putting `exec mako` in your compositor's configuration file.
 
 ## Configuration
 

From 5fea601bc4399f73ec21d728707906ecafa83e95 Mon Sep 17 00:00:00 2001
From: o0nd7ots <124466962+o0nd7ots@users.noreply.github.com>
Date: Wed, 20 Mar 2024 11:20:15 +0000
Subject: [PATCH 2/3] Changes reflecting feedback

---
 README.md | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 08545b6..de801ee 100644
--- a/README.md
+++ b/README.md
@@ -12,11 +12,9 @@ Feel free to join the IRC channel: #emersion on irc.libera.chat.
 
 ## Running
 
-`mako` requires an active session bus to function properly. 
-
-If you are using SystemD `mako` will run automatically when a notification is emitted.
-This happens via D-Bus activation, so you don't really need to explicitly 
-start it up (this also allows delaying its startup time and speed up system startup).
+`mako` targets the FreeDesktop notification specification.
+This means, that it assumes that there is a D-Bus session available at it's runtime.
+Systemd sets up a session bus by default so if you are using it, you are golden.
 
 If you are not using systemd, you might need to manually start a dbus user session
 with the compositor of your choice from the display manager. The command run should

From 77c53014643c45ac51fac0d04dcef856b7c7f916 Mon Sep 17 00:00:00 2001
From: o0nd7ots <124466962+o0nd7ots@users.noreply.github.com>
Date: Wed, 20 Mar 2024 11:20:57 +0000
Subject: [PATCH 3/3] Deduplicated info

---
 README.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/README.md b/README.md
index de801ee..6f82b67 100644
--- a/README.md
+++ b/README.md
@@ -12,8 +12,7 @@ Feel free to join the IRC channel: #emersion on irc.libera.chat.
 
 ## Running
 
-`mako` targets the FreeDesktop notification specification.
-This means, that it assumes that there is a D-Bus session available at it's runtime.
+`mako` assumes that there is a D-Bus session available at it's runtime.
 Systemd sets up a session bus by default so if you are using it, you are golden.
 
 If you are not using systemd, you might need to manually start a dbus user session