It's true. I rarely look there. bug-bash is the preferred conduit for
bug reports.
> https://savannah.gnu.org/support/index.php?108163
> probably invalid, pasting giant buffers into bash loses characters
> because of lack of pseudo tty flow control, not bash's fault.
Interestingly enough, a few enterprising people (Margarita Manterola,
Maximiliano Curia) put significant time into this and discovered a problem
with tty input queue management in the Linux kernel. The most recent
message thread is here:
http://lists.gnu.org/archive/html/bug-readline/2013-11/msg00005.html
----
Depends on the actual bug -- but one instance of this is where bash loses
chars but not, say, 'cat' , -- but both go through the tty code.
In bash, random 'COMPLETION' chars, besides not being taken as 'input',
can also cause a prompt to come up with swallows more input.
Maybe bash needs a "set paste/nopaste" type option (but properly bashicised)
like vim has to resolve a similar problem.