Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Bonk, a command-line tool for X11 window management

github.com

Post reply on HN
Print view View original

41–50 of 70 posts

Re: Show HN: Bonk, a command-line tool for X11 window management

#41

Post by somat »

bitwize wrote: post #18
GuB-42 wrote: post #11

Earlier quoted context omitted.

The question is "when?". Wayland is 15 years old, it already had a lot of time to "get better". So today, in most cases, I'd say X11 is still the way to go, it just works better. When Wayland will get better and apps start supporting Wayland more than they support X11, it will be the time to switch, but at the glacial pace Wayland advances, chances are that your current system will be obsolete when it will happen. It…

> The question is "when?". Wayland is 15 years old, it already had a lot of time to "get better". So today, in most cases, I'd say X11 is still the way to go, it just works better. If you run more than one monitor with different DPI, Wayland is the only choice. If you want to do HDR, Wayland will be the only choice. > When Wayland will get better and apps start supporting Wayland more than they support X11, it will b…

X11 has supported mixed dpi from nearly the very beginning.

http://wok.oblomov.eu/tecnologia/mixed-dpi-x11/

Re: Show HN: Bonk, a command-line tool for X11 window management

#42

Post by DonHopkins »

shmerl wrote: post #9
o11c wrote: post #7

Earlier quoted context omitted.

Wayland is still buggier than a swamp. At this point they're no longer showstopping bugs, but if you don't want to be constantly annoyed by little things not working, X11 is still the way to go.

Buggier or not - it's too late to think X11 is the alternative. It's not. Wayland is going to get better for whatever is needed. X11 is absolutely not the way to go.

X11 was absolutely not the way to go since the day it was released on 15 September 1987, but that never stopped it.

Re: Show HN: Bonk, a command-line tool for X11 window management

#43

Post by rendaw »

FascinatedBox wrote: post #3
compressedgas wrote: post #2

This does not appear to do anything that xdotool doesn't already do.

This solves a few issues in xdotool for me: Window selection allows for multiple criteria at once, and I can also reject windows. I'm also able to use the window manager's client list as a source, which makes getting toplevel windows much easier. Window movement is done using static gravity, fixing an issue where windows were moving differently if they were a terminal window versus non-terminal window. Bonk can delet…

GP's question seems like it might be a common question. Would it make sense to add this to the readme?

Re: Show HN: Bonk, a command-line tool for X11 window management

#44

Post by FascinatedBox »

jdiff wrote: post #12
FascinatedBox wrote: post #3

Earlier quoted context omitted.

This solves a few issues in xdotool for me: Window selection allows for multiple criteria at once, and I can also reject windows. I'm also able to use the window manager's client list as a source, which makes getting toplevel windows much easier. Window movement is done using static gravity, fixing an issue where windows were moving differently if they were a terminal window versus non-terminal window. Bonk can delet…

Can it send whatever signal it is that WMs do when a window is fullscreened, or block the signal sent when it's unfullscreened? If so, I'm 100% sold.

Yes, through the state option (xdotool calls it windowstate). I was confused when implementing it, because there appear to be three different fields: maximized_horz, maximized_vert, and fullscreen. If you want total fullscreen (covers taskbar and other stuff), use the last one. If you want the window maximized, use both of the maximized ones.

Come to think of it, I should put in better documentation for the state option, as well as a general maximize alias.

Re: Show HN: Bonk, a command-line tool for X11 window management

#45

Post by FascinatedBox »

rendaw wrote: post #43
FascinatedBox wrote: post #3

Earlier quoted context omitted.

This solves a few issues in xdotool for me: Window selection allows for multiple criteria at once, and I can also reject windows. I'm also able to use the window manager's client list as a source, which makes getting toplevel windows much easier. Window movement is done using static gravity, fixing an issue where windows were moving differently if they were a terminal window versus non-terminal window. Bonk can delet…

GP's question seems like it might be a common question. Would it make sense to add this to the readme?

Good point. I'll make a note to add some documentation to that effect. I didn't think of it originally because I didn't expect this much interest in my project.

Re: Show HN: Bonk, a command-line tool for X11 window management

#47

Post by bee_rider »

t-3 wrote: post #39
kiwijamo wrote: post #15

Earlier quoted context omitted.

It depends a lot on your desktop enviornment/window manager, distro, hardware, etc. I personally find Wayland works perfectly out of the box whereas X11 still to this day has issues with basic stuff like screen tearing that needs me to add a line to my xorg config file to enable the driver feature that stops screen tearing. (Note that every other display server has zero issues -- MacOS, Windows, Wayland, etc so the f…

What are you running when you experience screen tearing? I've literally never once encountered it in over 20 years of using X.

IIRC I get it in Firefox occasionally. I vaguely suspect some combination of smooth scrolling, video, and a portrait mode screen but it isn’t annoying enough to investigate

Re: Show HN: Bonk, a command-line tool for X11 window management

#48

Post by omnimus »

t-3 wrote: post #39
kiwijamo wrote: post #15

Earlier quoted context omitted.

It depends a lot on your desktop enviornment/window manager, distro, hardware, etc. I personally find Wayland works perfectly out of the box whereas X11 still to this day has issues with basic stuff like screen tearing that needs me to add a line to my xorg config file to enable the driver feature that stops screen tearing. (Note that every other display server has zero issues -- MacOS, Windows, Wayland, etc so the f…

What are you running when you experience screen tearing? I've literally never once encountered it in over 20 years of using X.

Maybe you are not sensitive to it. Some people dont percieve tearing as much as others. I run base PopOS (ubintu derivative with gnome) and i get tearing in x. I don’t know much about linux jist that when i login i can choose x/wayland and wayland seems to be a lot better at everything (fractional scaling also works).

Re: Show HN: Bonk, a command-line tool for X11 window management

#49

Post by omnimus »

somat wrote: post #41
bitwize wrote: post #18

Earlier quoted context omitted.

> The question is "when?". Wayland is 15 years old, it already had a lot of time to "get better". So today, in most cases, I'd say X11 is still the way to go, it just works better. If you run more than one monitor with different DPI, Wayland is the only choice. If you want to do HDR, Wayland will be the only choice. > When Wayland will get better and apps start supporting Wayland more than they support X11, it will b…

X11 has supported mixed dpi from nearly the very beginning. http://wok.oblomov.eu/tecnologia/mixed-dpi-x11/

Yet it doesnt seems to work (from nearly the very begining).

Re: Show HN: Bonk, a command-line tool for X11 window management

#50

Post by bee_rider »

shmerl wrote: post #36
donio wrote: post #35

Earlier quoted context omitted.

Besides the limitations others have mentioned users should be aware that since ydotool works by writing events directly into /dev/uinput the input will go to whatever happens to be focused at the moment. It will happily type your secrets into a chat window if you move the mouse at the wrong time. There is no way to do the equivalent of xdotool type --window 0x600005 "my important input"

It's not like xdotool is so secure in the first place. X11 is one huge hole from that perspective. Anything can read anything and all your important input can be read by some other window anyway.

This is a totally different issue; Wayland gives up the ability to provide user-aid that prevents an obvious human error. This is not really a security issue, it is a usability issue that can just happen to allow a user to make a security slip-up.

In exchange, Wayland gains… well, nothing really, the idea is that it’ll protect users from malicious programs peeking at other windows on their computer. But in that case situation is already FUBAR, there’s no way to protect a computer that is already running attacks locally on itself.

Post reply on HN