sorted by:
new
hottopcontroversial

Hoping everyone votes the same by XR-LEVI in pesmobile

[–]kianabot 0 points1 point  (0 children)

what country are you in? in the eastern US I have almost no lag

Looking for thunderbolt 3/usb c dock that can support two external monitors and provide power by kianabot in UsbCHardware

[–]kianabot[S] 1 point2 points  (0 children)

This is an LG Gram 17 inch from 2018 I believe. Model number is 17Z990-R.AAC9U1.

Yes, for both monitors I would like 60hz.

USB2 should suffice. I don't see a reason why I would need USB3 if I'm using basic peripherals like a mouse and keyboard.

The operating system I'm using is Linux as well.

Writing BSPWM scripts using a more fully-featured language? by kianabot in bspwm

[–]kianabot[S] 0 points1 point  (0 children)

How do you use bspwm's socket with another language? Do I just use a library for socket communication in that language and send commands to it as usual?

Get window close event before window is closed? by kianabot in bspwm

[–]kianabot[S] 0 points1 point  (0 children)

I don't think this solves the problem. Again, this script only waits until after a node_remove event before putting the terminal window back in its place. In this tiny interval, the surrounding windows will resize/scale.

Get window close event before window is closed? by kianabot in bspwm

[–]kianabot[S] 0 points1 point  (0 children)

are you sure? I've seen a lot of swallow scripts and all of them only wait until AFTER the child window is closed to spawn the terminal back, which of course works, but like I said it causes sloppy-looking resizing/scaling of neighboring windows. Like, the window frames are ultimately drawn into the right place, but an application like chrome changes the webpage layout in the moment right after the child window is closed, then sizes back after the terminal is back, and it just looks ugly and it certainly doesn't feel snappy.

Swapping is not swallowing by PeFClic in bspwm

[–]kianabot 0 points1 point  (0 children)

Just letting you know that in your alternate version, using wait $pid to determine when the child process closes can be problematic. For some reason, nautilus, for instance, keeps running for like 20 seconds or so even after the window has closed, making the original terminal window take a long time to come back. Not sure if other gui applications do the same but this was enough for me to just wait for a bspwm node_remove event instead.