---
 scripts/core/sxmo_status.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/core/sxmo_status.sh b/scripts/core/sxmo_status.sh
index 374983b..45bfae8 100755
--- a/scripts/core/sxmo_status.sh
+++ b/scripts/core/sxmo_status.sh
@@ -54,7 +54,7 @@ del() {
 	shift
 
 	if [ -z "$id" ]; then
-		printf "usage: %s rm <id>\n" "$(basename "$0")" >&2
+		printf "usage: %s del <id>\n" "$(basename "$0")" >&2
 		exit 1
 	fi
 
-- 
2.35.1

---
 configs/default_hooks/sxmo_hook_start.sh | 4 ++++
 scripts/core/sxmo_wob.sh                 | 4 +++-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/configs/default_hooks/sxmo_hook_start.sh b/configs/default_hooks/sxmo_hook_start.sh
index 5270284..7b93c54 100644
--- a/configs/default_hooks/sxmo_hook_start.sh
+++ b/configs/default_hooks/sxmo_hook_start.sh
@@ -15,6 +15,10 @@ echo "unlock" > "$SXMO_STATE"
 
 case "$SXMO_WM" in
 	sway)
+		# This env var requires sxmo to be started, hence we can't set
+		# it in profile
+		# useable_width="$(swaymsg -t get_outputs -r | jq '.[] | select(.focused == true) | .rect.width')"
+		# export WOB_ARGS='-W "$((useable_width - 60))" -a top -a left -a right --border-color "#DBCBA2AA" --background-color "#000000AA" --bar-color "#DBCBA2AA" -b 1 -M 10'
 		sxmo_daemons.sh start desktop_notifier mako
 		sxmo_daemons.sh start wob sxmo_wob.sh
 		sxmo_daemons.sh start menu_mode_toggler sxmo_menumode_toggler.sh
diff --git a/scripts/core/sxmo_wob.sh b/scripts/core/sxmo_wob.sh
index ae2911f..075fa9b 100644
--- a/scripts/core/sxmo_wob.sh
+++ b/scripts/core/sxmo_wob.sh
@@ -9,13 +9,15 @@
 . "$(which sxmo_common.sh)"
 
 useable_width="$(swaymsg -t get_outputs -r | jq '.[] | select(.focused == true) | .rect.width')"
+default_args="-W $((useable_width - 60)) -a top -a left -a right -M 10"
+WOB_ARGS="${WOB_ARGS:-$default_args}"
 wob_sock="$XDG_RUNTIME_DIR"/sxmo.wobsock
 rm -f "$wob_sock"
 mkfifo "$wob_sock"
 
 # By opening the socket as read-write it isn't closed after the first write
 # see https://unix.stackexchange.com/questions/392697
-wob -W "$((useable_width - 60))" -a top -a left -a right -M 10 <> "$wob_sock" &
+wob $WOB_ARGS <> "$wob_sock" &
 WOBPID=$!
 
 finish() {
-- 
2.35.1

sxmo-utils/patches/.build.yml: FAILED in 24s

['sxmo_status.sh del' help typo][0] from [Bruno Dupuis][1]

[0]: https://lists.sr.ht/~mil/sxmo-devel/patches/30646
[1]: bruno.dupuis@protonmail.com

✗ #725626 FAILED sxmo-utils/patches/.build.yml https://builds.sr.ht/~mil/job/725626

Marked as superseded

Hey! just for my information... Is it possible to mark a patch as superseded myself? How so? It would remove the burden of cleaning my own mess from the shoulders of the maintainers...

Thanks!

--
Bruno Dupuis

------- Original Message -------

On Tuesday, March 29th, 2022 at 11:34, Stacy Harper <contact@stacyharper.net> wrote:

> Marked as superseded

Hey there,

Nah I dont think you can. Ideally sourcehut will be able to handle
common cases itself. Sending a v2 with the same title should be enough.

This is a planned feature we all wait :D

Thanks for your patchs !