ortango

>``bspc desktop `primary`:^1 -f`` are those backticks a visual artifact, or are they in the command? they should not be. bspc desktop primary:^1 -f other then that i have not...

oh. it's a zsh error. if you have EXTENDED_GLOB on you need to either quote or `\` escape the carat. bspc desktop primary:\^1 -f # or bspc desktop "DP-3:^1"

>`zsh: no matches found: primary#next:^1` that is a zsh error again. with **extended glob** active you need to also escape hashes. for those types of errors you should check the...

01107f9 , 4b6f3761b0094fd911de84b1b0ccd2f3721b7a19 - is newer then ver 0.9.10. i'd guess that is the issue. my apologies, i didn't realize that commit isn't in a release.

there have been a decent amount of commits since last release, but yeah it's been a while.

Running linux here and everything seems to be working fine with the patch. I tried getting some zombied processes in bspwmrc and subscribe seems to work fine. I needed to...

The perl commands act as expected, pipe ignore version with perm errors to stderr and normal version exits immediately. Not sure why I'm not getting the sig_ign behavior you get....

adding a small example: #window is focused on ^1 $ bspc query -N -n focused.window 0x01200027 #create receptacle on ^2 $ bspc node @^2:/ -i $ bspc query -N -d...

It's worth saying that the config `ignore_ewmh_fullscreen` exists for bspwm and `full-screen-api.ignore-widgets` exists for firefox. Neither of them work without some hiccups though. eg, firefox (with ignore-widgets) will do what...

i think the 12 characters are a red herring. pretty sure this is just the standard race issue between rules and window properties. it happens when bspwm gets the window...