In article <p4qtis$avs$1...@dont-email.me
Lew Pitcher <lew.p...@digitalfreehold.ca
>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.
>> 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.
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL: