commit 7085057f6d75a259a399e6e0e65291804d7ceb18
parent 8c79f8dc155ba696572be30ee8c2ddfc577ae418
Author: Leonardo Hernández Hernández <leohdz172@proton.me>
Date: Wed, 11 Oct 2023 19:58:18 -0600
update README.md
these things were changed in the code but not in the readme
Diffstat:
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
@@ -27,7 +27,7 @@ given the base on which it is built. Implemented default features are:
monitoring
- Provide information to external status bars via stdout/stdin
- Urgency hints via xdg-activate protocol
-- Support screen lockers via input-inhibitor protocol
+- Support screen lockers via ext-session-lock-v1 protocol
- Various Wayland protocols
- XWayland support as provided by wlroots (can be enabled in `config.mk`)
- Zero flickering - Wayland users naturally expect that "every frame is perfect"
@@ -83,6 +83,7 @@ When dwl is run with no arguments, it will launch the server and begin handling
any shortcuts configured in `config.h`. There is no status bar or other
decoration initially; these are instead clients that can be run within
the Wayland session.
+Do note that the background color is black.
If you would like to run a script or command automatically at startup, you can
specify the command using the `-s` option. This command will be executed as a
@@ -106,7 +107,7 @@ automatically, you will need to configure it prior to launching `dwl`, e.g.:
### Status information
-Information about selected layouts, current window title, and
+Information about selected layouts, current window title, app-id, and
selected/occupied/urgent tags is written to the stdin of the `-s` command (see
the `printstatus()` function for details). This information can be used to
populate an external status bar with a script that parses the information.
