Google| Subject | Re: Ping Owl: More examples of "window 1" |
| From | Snit |
| Date | 09/24/2016 03:21 (09/23/2016 18:21) |
| Message-ID | <D40B2336.7E3A8%usenet@gallopinginsanity.com> |
| Client | |
| Newsgroups | comp.os.linux.advocacy |
| Follows | Octavian W. Lagrange |
On 9/23/16, 4:40 PM, in article adsfhu4e0.g4@perch.invalid, "Octavian W. Lagrange" <olagrang@perch.invalid>wrote:
Octavian W. LagrangeGood grief your trolling is getting more and more stupid. Here is how your current trolling is going:
Snit <usenet@gallopinginsanity.com>wrote:SnitOctavian W. Lagrange
On 9/23/16, 2:28 PM, in article adhg93g0.gji@perch.invalid, "Octavian W. Lagrange" <olagrang@perch.invalid>wrote:Octavian W. LagrangeSnit
Snit <usenet@gallopinginsanity.com>wrote:SnitOctavian W. Lagrange
On 9/23/16, 2:08 PM, in article slkabie.atee3@perch.invalid, "Octavian W. Lagrange" <olagrang@perch.invalid>wrote:
...SnitOwl's new trolling nonsense is when he spoke of "Script1 inadvertently sends something to Script2's window" he did not mean Script2's window. LOL!Octavian W. Lagrange
So when you say "the scripts windows are not even the ones beign discussed" you are not referring to whatever window (if any) that the script might have been executed in? If not, then which "script's windows" would *you* be referring to when you said that?
I am not talking about ANY of the script windows (other than the ones where the scripts are in)...
Oh so you mean those "scripts' windows" that aren't the "scripts' windows" because they "belong to the Terminal"? Is that the ones?
LOL!
Seriously, the more you talk the more you show how little you know. Some basic facts for you:
* Scripts can run in windows but they need not. Even if they do, though, they are not the ones being controlled, nor do they in any way "own" any of the windows which are being controlled by the scripts.
* The ONLY windows being controlled by these scripts are the ones from the terminal. In these cases the windows can be referenced by ID, index, and more but in NO case are they in a situation where another script cannot control them at ANY time, even in the middle of one script running.
This has been explained to you about a dozen times in a dozen ways... but still you say this:
Owl: ---- Script1 inadvertently sends something to Script2's window" -----
And then when asked what you mean you deny you mean Script2's window.
What is "Script 2's" window? Snit:
"The scripts windows are not even the ones being discussed!"
What did you mean by "the scripts windows"?
Owl: ----- For example, Script1 inadvertently sends something to Script2's window: ... ------
Snit: ----- The scripts windows are not even the ones being discussed! It is the terminal windows which are having things done with them! This is a concept you keep getting wrong over and over and over. -----
Owl: ----- What the FUCK are you babbling about NOW? I am NOT talking about the script's window you MORON. -----
WTF? So you asked about the scripts windows but then denied you were talking about the scripts windows AS you call me names. How clever of you. And I called you out on this:
Snit: ----- Ah, so when you said: "Script1 inadvertently sends something to Script2's window" you did not mean Script2's window. -----
And instead of actually noting how much you fucked up, you tried to turn things around:
Owl: ----- What did you mean by "the scripts windows"? -----
Let me clear things up for you AGAIN (though at this point it is clear you are just trolling):
* The ONLY windows being controlled by these scripts are the ones from the terminal. In these cases the windows can be referenced by ID, index, and more but in NO case are they in a situation where another script cannot control them at ANY time, even in the middle of one script running.
* I am the one who taught you this (and even after you were told you kept asking) and then you trolled and pretended I did not know this or did not understand the implication of referencing windows by ID or index!
* Scripts can run in windows but they need not. Even if they do, though, they are not the ones being controlled, nor do they in any way "own" any of the windows which are being controlled by the scripts. Again, ANY script can send messages to ANY window... by index, ID, or more.
* The script editors' windows (the one the scripts are in) are NOT being controlled by the scripts we have been looking at. They COULD be, but they are not. These windows (the scripts' windows) are completely irrelevant to the conversation EXCEPT when you keep talking about them and use the term "script's windows" to maybe (mean) the terminal's windows because that is how lost you are!
* When I respond to you speaking of the "script's windows" and note you are lost, I mean whichever windows you are talking about: either the windows of the script editor, which is not relevant, or the windows the scripts are referencing which are NOT the script's windows but you are too lost to understand that!
As you keep trolling I will feel free to keep posting the same text (maybe with slight modifications to account for your inevitable twists of your trolling)... at least until you are able to move forward and not just ask the SAME questions over and over and over that the above text answers! Of course, I will do so ONLY in response to your trolling... and then those that troll COLA will blame ME for responding to your trolling with the same facts which rip your trolling to shreds.
It is not like this is the first time I have danced this dance.
-- * 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-
