Kory@lemmy.ml to linuxmemes@lemmy.world · 7 days agoTerminating a processlemmy.mlimagemessage-square87fedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1imageTerminating a processlemmy.mlKory@lemmy.ml to linuxmemes@lemmy.world · 7 days agomessage-square87fedilinkfile-text
minus-squareZozano@lemy.lollinkfedilinkEnglisharrow-up0·6 days agoI 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.
minus-squareFushuan [he/him]@lemm.eelinkfedilinkEnglisharrow-up0·6 days agoDunno, 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.
minus-squareZozano@lemy.lollinkfedilinkEnglisharrow-up0·6 days agoGreat idea, now I just need to know how to do that.
minus-squareHawk@lemmynsfw.comlinkfedilinkarrow-up0·6 days agoWhat’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.
I 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.