Package: bash Version: 5.2.37-1.1+b1 Followup-For: Bug #1036302 Despite Bernhard's efforts, this is still not fixed. Plus there's a bunch of similar sounding reports, a few on Debian's BTS alone, even if unclear whether it's the exact same issue. This one, probably connected to readline and for what I believe ancient, persists at any rate. I'm seeing it apparently randomly about once per week (then usually my xterm just disappears, session history lost) and it's getting hard to bear. Also hard to believe something so basic and still popular as bash/readline could be so buggy for so long.
Do other people/devs just never run into it? Are we others doing something wrong? I read in some places, perhaps in connection with similar bugs, that it seems to be related to "hard" bash or history usage; when you're working fast that is, and I think I can about confirm as much. It apparently only happens when I'm busy, but certainly never in the background or when I'm doing nothing. Still, bash should be able to handle this. Or else maybe not allow us to bind history search to keys to begin with, and this is a serious sugggestion. Or at least warn us against possible consequences. It has to be fixed in some way, any way. As it is however it's not good. Oliver
