diff options
| author | koekeishiya <aasvi93@hotmail.com> | 2019-03-07 22:48:36 +0100 |
|---|---|---|
| committer | koekeishiya <aasvi93@hotmail.com> | 2019-03-07 22:48:36 +0100 |
| commit | ef2e8ce70b164edecda2412855b60d100d5361a5 (patch) | |
| tree | 38e7c60d04cc7e890f9c3dc55dec6863b73ad515 | |
| parent | 3922cf456a6c711032a1a6650442be67cfbb80fb (diff) | |
| download | skhd-ef2e8ce70b164edecda2412855b60d100d5361a5.tar.gz skhd-ef2e8ce70b164edecda2412855b60d100d5361a5.zip | |
#54 add note regarding pid-file
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -4,6 +4,10 @@ (although rewritten from scratch), that sacrifices the more advanced features in favour of increased responsiveness and performance. **skhd** is able to hotload its config file, meaning that hotkeys can be edited and updated live while **skhd** is running. +**skhd** uses a pid-file to make sure that only one instance is running at any moment in time. This also allows for the ability to trigger +a manual reload of the config file by invoking `skhd --reload` at any time while an instance of **skhd** is running. The pid-file is saved +as `/tmp/skhd.pid` and so the user that is running **skhd** must have write permission to said path. + feature comparison between **skhd** and **khd** | feature | skhd | khd | |