Closed MatthiasCoppens closed 4 years ago
same thing will also happen with other things that start with a wm name (dwmblocks is a thing, right?)
Hello, can you see if 0ac1b7d216e7fbd84d53d1789a7c2581ffb464a3 fixes it for you? Thanks.
@elkowar I'm not sure about dwmblocks, but I had my borders script named 2bspwm
for a bit and it detected that as the WM, so I undid the rename.
Sadly sh sorts stuff like 1 20 3 388 4
so it doesn't go from lowest PID to highest, sort
has the -n
option which fixes this, but that's not really a builtin so I can't use it.
Can confirm that https://github.com/6gk/fet.sh/commit/0ac1b7d216e7fbd84d53d1789a7c2581ffb464a3 fixes it on my end
In the WM case statement, i3blocks is considered to be a valid name:
https://github.com/6gk/fet.sh/pull/14 fixes it on my system, but that's only because I don't randomize my PIDs. If I were to do that, i3blocks would still show up as my WM 50% of the time.