Ok, I tested and mIRC does in fact /say both lines when pasting eg.
"Hello.
a"
Which is really weird, because the second line does not contain a linechange at the end and mIRC should have no reason to /say it. I don't know of a single possible reason why someone would want to paste and let mIRC automatically /say even a single line. I would say that nine out of ten times it is done by accident. If for some reason you need to paste and say multiple lines, you're doing something wrong. This was a good feature before services like pastebin or paste2, but
today it's a completely worthless bug rather than a feature.
Why are you people defending these bugs by trying to convince others and yourself that these bugs aren't bugs? I bet it's the reason why everything else gets updated over the years and mIRC still looks like it just came out in 1995.
The "right way" would be for mIRC to only ask for confirmation when the actual number of lines being pasted are greater than the min threshold in your settings. Since a blank line is not pasted, it shouldn't count to the number of lines
But the blank line
IS pasted, mIRC just ignores it and doesn't /say it because it's empty.
EDIT: Don't confuse what's being pasted and what mIRC /says. This issue is about the actual number of pasted lines. Not what mIRC thinks is being pasted but what's being
actually pasted.
