wmutils / opt Goto Github PK

wm: bspwm v0.9.7-10

sxhkd no longer supports the feature that replaced xmmv, so it's needed again.

It'd also be nice if you could resize windows w/ xmmv, albeit that might be asking too much.

Hi,

I think you made a typo in README.md at the first line:

"opt is at set of optional utilities meant to accompany core."

Regards.

How can I build on FreeBSD? I have all the xcb libs installed but can't find them

Just a reminder that this bit of the code is ridiculous and needs fixing/explanation.

I was trying to use the script written by https://github.com/neeasade/dotfiles/blob/master/wm/.wm/scripts/visual/2bspwm provided by @neeasade which uses chwb2 to draw on borders
which didn't work, nor it was giving out any output.
On finding out the problem, I realise that chbw2 is not working as it was exepected ( I use bspwm )
It was not giving out any output or visual change.
Later on , I tried chwb to draw border so that another border may be drawn using chwb2 over it,
But on bspwm, all chwb is doing is changing the border color temporaly until I refocus the mouse on that window, whereas if I use the -size arguement , then the window seems to shift a bit toward left corner without any change in border size
Can you please help me figuring this out....
Thanks in advance

Hello! I am running CWM on OpenBSD 7.3 and wanted to use chwb2 to add two borders around the window. However i can’t get it to work. I create a border using chwb and that works, i can change color and width but when i use chwb2 utility nothing happens, no output, warning or change of any kinds, it just runs. Any idea what am i doing wrong? Thx, cheers!

The primary function in xmmv.c besides the main loop is mresize. This makes sense in xmrs.c but I think it's confusing in xmmv.c, particularly as both files have an mresize.
mmove would be better.

Similar issues if you uncomment XCB_EVENT_MASK_BUTTON_PRESS in the source and compile it with XCB_EVENT_MASK_ENTER_WINDOW enabled.

I also recorded an example.

when using wew -m 4 the mouse click doesn't pass through to the window

Hello !
First of all, thanks for providing these tools,
while trying to get chwb2 working on bspwm I noticed that there wasn't any effect on the window, I ran this command from the man page:
chwb2 -O 000000 -I ffff00 -i 3 -o 1

Can you help me? As there aren't really any other example of this utility...
Thanks

Hello. I try to watch mouse pointer events using wew, although I recieve incorrect, I believe, data from wew programm.
For example, if I try
wew -m XCB_EVENT_MASK_KEY_PRESS
wew does not return anything at all on key press but it returns fsts on creating a client(wid is random here just for an example):
16:0xasd23234
19:0xasd23234
the same goes for XCB_EVENT_MASK_BUTTON_MOTION, I havent tested the other event masks.

Hello,

I've recently updated to the latest git version of chwb2 and I've noticed that for windows that have some transparent property now get transparent borders with an incorrect color for the inner border. Before updating, the borders would simply be solid of whatever color I set them to be in my bspwmrc. If I kill picom, I get the expected behavior of two window border colors. I guess I was wondering if anyone knew if there was a proper setting in picom to ignore transparent borders? I've attached a screenshot showing the current behavior while picom is running. The window on the left has the unusual behavior while the expected behavior is on the right.

Here's another screenshot showing the same screen but picom killed. The borders are now behaving as expected.

Did the formatting of wew output change? The man page says that the output will be a int:widhowever I am getting a string and wid seperated by a tab character.

For example
DESTROY 0x00000001
instead of
17:0x00000001

When xmmv is called from polybar, it does not work properly: the window follows the cursor, but the window is not placed on keydown: the keydown just "goes to the window" (you will have to run killall xmmv to "place the window")

How to reproduce

1. create a script which calls xmmv (/path/to/script):

#!/bin/bash

xmmv

2. create a button in polybar:

[module/my_button]
type = custom/text
content = I_AM_A_BUTTON
click-left = /path/to/script

if you don't know how to use polybar or you just don't use it, use this minimal config file (/path/to/cfg):

[bar/minimal]
modules-center = my_button

[module/my_button]
type = custom/text
content = I_AM_A_BUTTON
click-left = /path/to/script

launch polybar by running this command polybar -c /path/to/cfg minimal

NOTE:
I found this bug while making a bspwm script, in which I passed an argument to xmmv, so the lack of arguments is not the issue.
I also tried xmmv "$(pfw)", xmmv &, xmmv & disown, they don't fix anything.
The output of pfw is correct even when launched with polybar: I checked it with this script
/path/to/script:

#!/bin/bash

wid="$(pfw)"
notify-send "$wid"
xmmv "$wid"

EDIT:
In order to reproduce the bug you also need to make /path/to/script executable: chmod +x /path/to/script
I also tried:

#!/bin/bash

wid="$(pfw)"
wtf "$wid"
xmmv "$wid"

but it didn't fix the issue.
And I also tried:

#!/bin/bash

wid="$(pfw)"
sleep 2
xmmv "$wid"

I clicked on the window during the 2 seconds of sleep and it did fix the issue.

Here's the error Emacs gives me when I run it in the CLI: http://sprunge.us/OiBL

This happens if I have wew -a running in another terminal, but if I close wew it works again, if I start wew again then it doesn't work anymore, which makes me think it's definitely wew.

I'm using bspwm if that matters, although I don't think it does.

So this crashes Emacs if I try starting it, but if Emacs is already running it doesn't crash it.

Any ideas why this might happen? Need any more info?

If you move your mouse too quickly from one window to another, wew won't catch event number 7 (XCB_ENTER_NOTIFY), preventing my script from properly working.

Since it's seems that the event triggers on the window's border and I'm testing everything on a virtual machine before I do a real install, it could be because the VM is too slow, but I'm not sure about that.

how do apps manage their fullscreen state? for instance sxiv -fr . does not start in fullscreen. wew doesn't appear to listen to fullscreen requests. do you fullscreen the app twice, through the app's interface, as well as with wmutils?

Due to the glitch that people are experiencing in the other open issue surrounding wew event 7, I thought I would try and and focus my windows by using a button press. However, wew produces no output at all to my shell when I press any button on my mouse. Any ideas?

I'm not 100% that this isn't intended behavior, but here it goes.

I wanted to implement focusing windows with click (instead of hover), but starting wew with a mask wew -m 4 (XCB_EVENT_MASK_BUTTON_PRESS) grabs the click event (the event is registered in wew) but doesn't pass it to the window underneath the cursor.

Am I doing something wrong or is this how the program should behave?

how do you configure the xmmv resize window function in sxhkd? Thanks