Dunno, create a script that uses a program to get the process number of the current active window or the window the mouse is hovering, and then kill that? Bind that script inor a key with whatever program and voilá.
Get learning lol. I know that there’s some command line program that gives process info on mouse hover and then that can be parsed with awk to get the pid, then pipe that again into kill -kill. Then use xbindkeys or whatever keybindings program to bind that script to a key.
Tbh. For involved stuff like this chatgpt will help you more than stackoverflow.
Is there a Wayland equivalent?
Open the process list in your system monitor of choice, right click, signal, sigkill.
You can also open a monitor and use top or any variant to detect the process number and manually
kill -KILL numberI really want the convenience of binding xkill to a key, which I can use to double tap programs like the undead zombie they’ve become.
Dunno, create a script that uses a program to get the process number of the current active window or the window the mouse is hovering, and then kill that? Bind that script inor a key with whatever program and voilá.
It’s more involved sure but there’s your option.
Great idea, now I just need to know how to do that.
What’s your desktop environment? I’m pretty sure hyperland and sway will give a json output of open Windows.
You could parse that with jq and pipe it into fzf or dmenu?
Not quite the same as the clicking but probably just as quick.
Get learning lol. I know that there’s some command line program that gives process info on mouse hover and then that can be parsed with awk to get the pid, then pipe that again into kill -kill. Then use xbindkeys or whatever keybindings program to bind that script to a key.
Tbh. For involved stuff like this chatgpt will help you more than stackoverflow.
deleted by creator
xkill isn’t a function of Wayland.
I dunno; I sadly can’t use Wayland yet bc I have Nvidia
I don’t know if you heard, but the Nvidia issues are solved (mostly).
The issue most people had was with Explicit Sync, which was patched in the proprietary Nvidia driver 555 which is upstream on most distros.
Good to know; I’ll check it out!
idk if this could be subjective, but what do you mean by upstream here? Does that mean it’s included in most distros?
Yep. Most modern distros should be providing the 555 driver by now.