I've discovered something a little annoying about xkill.
That is, there doesn't seem to be any way to get out of it without killing anything. Nothing in the man page suggests any way to do this.
Am I missing something? Is there a way?
Kenny McCormack wrote:
I've discovered something a little annoying about xkill.
That is, there doesn't seem to be any way to get out of it without killing >> anything. Nothing in the man page suggests any way to do this.
[snip]
Am I missing something? Is there a way?
The man page seems to give clues...
"If a pointer button is pressed over a non-root window, the server will
close its connection to the client that created the window."
"-button number
This option specifies the number of pointer button that should be
used in selecting a window to kill. ... By default, the first button
in the pointer map (which is usually the left-most button) is used."
It looks like, if you don't specify "any" (that is, if you let the button >number default), then the /other/ buttons will _abort_ the kill.
Try aborting by pressing the right (or centre) mouse button (assuming that >you didn't specify that button as the kill button).
In article <p4qtis$avs$1@dont-email.me>,
Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
Kenny McCormack wrote:
I've discovered something a little annoying about xkill.
That is, there doesn't seem to be any way to get out of it without
killing
anything. Nothing in the man page suggests any way to do this.
[snip]
Am I missing something? Is there a way?
The man page seems to give clues...
"If a pointer button is pressed over a non-root window, the server will
close its connection to the client that created the window."
This implies that you can just click on the desktop background (which is a "root window" (right?)) and it will be a no-op (right?).
I've had mixed results with this. On at least one occasion, my system started acting generally weird after this - and I'm pretty sure that some system-critical desktop process had, in fact, been killed. So, I've
stayed away from this since then.
"-button number
This option specifies the number of pointer button that should be
used in selecting a window to kill. ... By default, the first
button in the pointer map (which is usually the left-most button) is
used."
It looks like, if you don't specify "any" (that is, if you let the button >>number default), then the /other/ buttons will _abort_ the kill.
Try aborting by pressing the right (or centre) mouse button (assuming that >>you didn't specify that button as the kill button).
Yes. That works. Thanks.
Given the default xkill commandline
xkill
I've tried a right-click on the desktop, which seems to dismiss xkill with >>no side effects. YMMV
Right - but that's because you "right clicked" and because we've now >established that right-clicking is the magic bullet for how to get out of >xkill without killing anything.
The issue is that before this thread's existence, I didn't know that and, >when I left clicked on the desktop (to get out of xkill), it killed something.
This implies that you can just click on the desktop background (which is a >> "root window" (right?)) and it will be a no-op (right?).
Given the default xkill commandline
xkill
I've tried a right-click on the desktop, which seems to dismiss xkill with
no side effects. YMMV
In article <p4qtis$avs$1@dont-email.me>,
Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
"If a pointer button is pressed over a non-root window, the server will
close its connection to the client that created the window."
This implies that you can just click on the desktop background (which is a "root window" (right?)) and it will be a no-op (right?).
I've had mixed results with this. On at least one occasion, my system started acting generally weird after this - and I'm pretty sure that some system-critical desktop process had, in fact, been killed. So, I've stayed away from this since then.
In article <p4r133$8af$1@dont-email.me>,
Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
...
This implies that you can just click on the desktop background (which is a >> "root window" (right?)) and it will be a no-op (right?).
Given the default xkill commandline
xkill
I've tried a right-click on the desktop, which seems to dismiss xkill with >no side effects. YMMV
Right - but that's because you "right clicked" and because we've now established that right-clicking is the magic bullet for how to get out of xkill without killing anything.
The issue is that before this thread's existence, I didn't know that and, when I left clicked on the desktop (to get out of xkill), it killed something.
Anyway, it is all good, so no worries now.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 353 |
Nodes: | 16 (2 / 14) |
Uptime: | 32:52:49 |
Calls: | 7,648 |
Files: | 12,809 |
Messages: | 5,698,908 |