[18:03] <laguna> say what is the deal with qterminal constantly crapping out when you hold a key down and let it repeat for several minutes....will they ever get this stuff working
[18:03] <laguna> every time there is a new version of lubuntu i check that and it never gets fixed
[18:04] <arraybolt3> laguna: I've never hit that bug, but, what usecase do you have where you have to hold down a key for several minutes?
[18:04] <arraybolt3> And what exactly is it doing wrong?
[18:04] <laguna> i never see that problem in the c++ kde terminal....or the c gnome terminal
[18:05] <laguna> arraybolt3 it is called trying to have the ability to type something....i can't understand why people don't check the buffer problems associated with their coed
[18:05] <laguna> code
[18:06] <laguna> at least thunderbird version 102.10 is working today
[18:06] <arraybolt3> laguna: You'll have to be more descriptive, because I still don't know what error is happening. Is QTerminal crashing? Does the cursor stop moving? Or something else?
[18:06] <laguna> arraybolt3 no just pick any key like say f on the keyboard and hold it down for a few minutes and watch the buffering crap out
[18:06] <arraybolt3> And also, again, *why* are you holding down a single key for several minutes? I can't think of a single command in QTerminal that uses "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" as part of it. :P
[18:07] <laguna> weeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeelllllllllllllllllllllllllllllllllll......what if you want to emphasize something
[18:07] <arraybolt3> If you hold down "e" for a few *minutes*, you're going to make a few *thousand* characters.
[18:07] <arraybolt3> But I'm testing now.
[18:08] <laguna> uh oh i see a problem with thunderbird too...it looks like it is chopping off some of the text i typed in the display window here
[18:09] <laguna> and they cannot say it is a c++ issue because kde is c++ and its terminal doesn't crap out
[18:09] <arraybolt3> laguna: Hmm, I see the problem that you're seeing.
[18:09] <arraybolt3> But if you type that many "f"s into your IRC client, I am going to get after you for flooding :P
[18:09] <laguna> oh well it won't be the first time.
[18:09] <arraybolt3> I assume there must be something that's looping through every character in the terminal every time a key shows up.
[18:10] <laguna> yea it is just shitty quality control on code people writ3e
[18:10] <laguna> write
[18:10] <arraybolt3> But still... I have no clue why anyone would need to do that. And even if you are doing that rather unlikely thing, it still works, it just slows down once you get far enough.
[18:11] <arraybolt3> I suppose it may be worth a bug in upstream LXQt.
[18:11] <laguna> arraybolt3 not really it will go to a dead halt if you wait long enough
[18:11] <arraybolt3> I don't have the patience to type that many characters :P
[18:11] <arraybolt3> And also I think Bash has a limit to how many characters it will accept in a single command.
[18:11] <laguna> i like the idea of lxqt but i don't like code with all kinds of problems
[18:11] <teward> laguna: unless you have a WPM typing speed of a billion, the buffers aren't *designed* to have the key repeat rate filling up the buffer, and that's typically *faster* than actual typing speeds
[18:12] <teward> also please don't swear in here, this is a public more friendly oriented channel so no need for profanity
[18:12] <laguna> teward not really my wife could type superfast when she was a hot young sexy secretary
[18:12] <teward> and if you don't like "code with problems" then I'm sorry to disappoint you but *all* code has problems.
[18:12] <teward> i won't ask you to keep it friendly in here and such again
[18:12] <laguna> teward tell me about it
[18:13] <teward> if you don't like LXQt because of a problem with its buffer rates, that's less to do about the code and more to do about your hardware, etc.  you're free to use *other* programs that "don't have this problem" but I'm not sure what you expect *us* to do short term on this kind of thing.
[18:14] <laguna> teward well its been my experience that usually nothing ever gets done but more constant corrections that never solve the problems
[18:14] <arraybolt3_> (internet glitchiness)
[18:14] <teward> then your experiences are blunted by the fact *you* had poor previous issues with programs, not the general reality of things
[18:15] <teward> you've reported this issue, but it's not necessarily going to be a 'quick fix' especially if the issue is at a core programming level
[18:15] <laguna> teward  facts are like assholes...everybody has one...but some are worth more than others
[18:15] <teward> and as arraybolt3 and myself have indicated we have never had this issue nor been able to replicate it (and I just tried on an Lubuntu 22.04 system)
[18:15] <teward> i also said stop with the profanity
[18:15] <arraybolt3> (I can reproduce the issue, I've just never managed to run into it in regular use.)
[18:16] <laguna> fuck off...let the bastards steal your wife and little kids and try to frame you for murder for 40 years and then see how you talk bastard
 moving on...
 Yes! (re @teward001: moving on...)
 It's not my place to say but contributors here are great and give a lot of time to help us. It is requested that all the members respect each other so the contributors and people who ask for help can both be happy and satisfied. Moving on...