On Mon, 6 Jul 2015 20:18:18 +0300 Alexander Kapshuk <alexander.kaps...@gmail.com> wrote:
> On Mon, Jul 6, 2015 at 8:01 PM, walt <w41...@gmail.com> wrote: > > My bash problem started a few weeks ago but I can't remember when. > > This problem is intermittent and hard to reproduce. I'm seeing it > > maybe less than ten times per day but often enough to be really > > annoying. > > > > This is the problem: occasionally bash gets in a state where it > > stops echoing the characters I type. The commands I type continue > > to work properly and I can see the output from them but I can't see > > the commands on the screen as I type them. > > > > So far I've seen this problem start *after* some bash command has > > finished executing, e.g. after doing 'git diff'. It never happens > > when I open a new xterm, before I run a command. > > > > I emerged app-shells/sash and I don't see the problem there, so I > > think this is a bash problem, but I'm just guessing. > > > > Any ideas? > > What's the output of 'stty -a'? Is the 'echo' attribute on, 'echo', or > off, '-echo'? I have the same symptoms as walt (except less often, probably because I'm typing in bash less often). The echo attribute is on for me. I think (but am not certain) the problem started for me when I updated bash and readline following this stabilization: <https://bugs.gentoo.org/show_bug.cgi?id=548756> In case it matters (and since I am using USE="-*"), here are my flags for those two packages. bash: nls readline -afs -bashlogger -examples -mem-scramble -net -plugins -vanilla sys-libs/readline: -static-libs ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32"
