Google| Subject | Re: Ping Owl: More examples of "window 1" |
| From | Snit |
| Date | 09/23/2016 20:13 (09/23/2016 11:13) |
| Message-ID | <D40ABEC3.7E2FE%usenet@gallopinginsanity.com> |
| Client | |
| Newsgroups | comp.os.linux.advocacy |
| Follows | Octavian W. Lagrange |
| Followups | Octavian W. Lagrange (11m) > Snit |
On 9/23/16, 10:26 AM, in article hugu7ae.jigue@perch.invalid, "Octavian W. Lagrange" <olagrang@perch.invalid>wrote:
...
Figured I should be more specific in my response here:SnitOctavian W. Lagrange
Well, you still have come a far way... it was not long ago you were talking about each script having its own window 1 for terminal, about having different instances of terminal... and even implications that if I referenced it with the ID and not the index that would prevent some other (hostile?) script compete with it.
I never said anything about *preventing another script* from targeting the window.
Owl: ----- Let's say two scripts are running, each making reference to Terminal's "Window 1". They each have to wait for something, then do something again with "Window 1". If we don't know which wait will complete first, is it possible for them to screw the pooch on this and do the "something" with the wrong window? -----
Other than preventing other scripts from targeting the window what could you possibly have been thinking of to prevent this? Remember, the script does not own the terminal window!
-- * OS X / Linux: What is a file? <http://youtu.be/_dMbXGLW9PI> * Mint MATE Trash, Panel, Menu: <http://youtu.be/C0y74FIf7uE> * Mint KDE working with folders: <http://youtu.be/7C9nvniOoE0> * Mint KDE creating files: <http://youtu.be/N7-fZJaJUv8> * Mint KDE help: <http://youtu.be/3ikizUd3sa8> * Mint KDE general navigation: <http://youtu.be/t9y14yZtQuI> * Mint KDE bugs or Easter eggs? <http://youtu.be/CU-whJQvtfA> * Easy on OS X / Hard on Linux: <http://youtu.be/D3BPWANQoIk> * OS / Word Processor Comparison: <http://youtu.be/w6Qcl-w7s5c>
09/22/2016-
