--
You received this message because you are subscribed to the Google Groups "xdotool-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xdotool-users+unsubscribe@googlegroups.com.
To post to this group, send email to xdotoo...@googlegroups.com.
Visit this group at https://groups.google.com/group/xdotool-users.
For more options, visit https://groups.google.com/d/optout.
WM_DELETE_WINDOW
" message?
"Typing in terminates the active window and bypasses any safeguards like "would you like to save your work?"." His problem with the current solution is that: |
" "xwit" is no longer part of the fedora repositories, and is not activally mantained" |
Best wishes from splitcells.net |
To unsubscribe from this group and stop receiving emails from it, send an email to xdotool-user...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "xdotool-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xdotool-users+unsubscribe@googlegroups.com.
Maybe, But the delete window function is a very basic (core X Windows) control that xdotool can not currently do.Another tool with this function is xclosedown which sends a delete (close) window event to all applications, then waits 30 seconds before sending the destroy (kill) event. Of course that is going a bit too far!
-JordanWe could support all 3. I don't think it will be much code.3) Add support to send a ClientMessage _NET_CLOSE_WINDOW to the window manager.A quick glance at this issue and some (very brief) research, it seems we have three options:2) Add support to send a ClientMessage with WM_CLOSE_WINDOW
1) Add support to invoke XDestroyWindow
On Mon, May 15, 2017 at 4:30 PM, Anthony Thyssen <a.th...@griffith.edu.au> wrote:
Maybe, But the delete window function is a very basic (core X Windows) control that xdotool can not currently do.Another tool with this function is xclosedown which sends a delete (close) window event to all applications, then waits 30 seconds before sending the destroy (kill) event. Of course that is going a bit too far!
kill_it=$(xdotool search --name Untitled getwindowpid);
kill $kill_it
That would not work for all applications. Applications don't set the clients PID. It also will not work for a remote X Window application running on another machine. Something I do all the time when administrating hundreds of machines!Also the report is to try and help improve "xdotool" with something very basic, that it should have, but for some reason does not.I am not trying solve a problem *I* am currently having.Anthony Thyssen ( System Programmer ) <A.Th...@griffith.edu.au>--------------------------------------------------------------------------DISCLAIMER - These opoi^H^H "damn", ^H, [esc :q :qq !q "shit!" :Q! "Whaddyamean, Not an editor command?" :wq! ^C^C^C !STOP ^bye ^quit :quit! !halt ...^w^q :!w :wq! ^D :qq!! ^STOP [HALT! HALT!!! "Why's it doing this?" :stopit!:wwqq!! ^Z ^L ^ESC STOP :bye bye bye! "Hey, what's this red button d..."--------------------------------------------------------------------------Anthony's Castle http://www.ict.griffith.edu.au/anthony/
On Tue, May 16, 2017 at 6:06 PM, Justin C <jtcha...@gmail.com> wrote:
Where Untitled is the title of the window
kill_it=$(xdotool search --name Untitled getwindowpid);
kill $kill_it
--
You received this message because you are subscribed to the Google Groups "xdotool-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xdotool-user...@googlegroups.com.