From 4411521f8ad1ed4df6c1bb003251ec1645c90704 Mon Sep 17 00:00:00 2001
From: Shaochang Tan <478710209@qq.com>
Date: Sun, 8 Oct 2023 09:21:01 +0200
Subject: [PATCH] update readme

---
 README.md | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 79bc825..b406db8 100644
--- a/README.md
+++ b/README.md
@@ -9,6 +9,7 @@ Compositors that are known to support the protocol are [Sway] and [Wayfire].
 The goal of this project is to allow precise adjustment of display settings in
 kiosks, digital signage, and other elaborate multi-monitor setups.
 
+
 ![Screenshot](wdisplays.png)
 
 # Installation
@@ -70,8 +71,16 @@ It's intended to be the Wayland equivalent of an xrandr GUI, like [ARandR].
 Sway, like i3, doesn't save any settings unless you put them in the config
 file. See man `sway-output`. If you want to have multiple configurations
 depending on the monitors connected, you'll need to use an external program
-like [kanshi] or [way-displays]. Integration with that and other external
-daemons is planned.
+like [kanshi] or [way-displays].
+
+When you apply a new change, the setting will be defaultly added to $HOME/.config/kanshi/config,
+if there is already a profile for the same monitors combination, the change will be applied on
+existing one.
+you can add kanshi autostart to your sway config:
+```
+exec_always pkill kanshi
+exec_always kanshi
+```
 
 ### How do I add support to my compositor?