https://bugs.kde.org/show_bug.cgi?id=401898
--- Comment #8 from Oswald Buddenhagen <o...@kde.org> --- that sendEOF stuff is all nonsense; it's already explained in bug #185140 why it's technically unnecessary. bash isn't the only process that will behave weirdly on EOF when a line has been started - just try an interactive 'cat'. also, this can't possibly work reliably, as only the foreground process will get the EOF. SIGHUP was introduced for a reason, after all. so as far as i'm concerned, that EOF stuff should be just reverted (including the workarounds that followed it). -- You are receiving this mail because: You are watching all bug changes.
