Re: bash-completion 1.2-1 breaks bash with tail -f

Alpha Fighter yahoo.com> writes: > > I've run into an issue with bash-completion v1.2-1.  After I tail -f a file and then press ctrl-c to stop > tailing I can no longer see any text I type.  My text is being entered, just not being ... echoed back. > > This does not happen after uninstalling 1.

Re: bash-completion 1.2-1 breaks bash with tail -f

Alpha Fighter yahoo.com> writes: > > I've run into an issue with bash-completion v1.2-1.  After I tail -f a file and then press ctrl-c to stop > tailing I can no longer see any text I type.  My text is being entered, just not being ... echoed back. > > This does not happen after uninstalling 1.

bash-completion 1.2-1 breaks bash with tail -f

I've run into an issue with bash-completion v1.2-1.  After I tail -f a file and then press ctrl-c to stop tailing I can no longer see any text I type.  My text is being entered, just not being ... echoed back. This does not happen after uninstalling 1.2-1.  It also does not happen if I downgrad

bash-completion 1.2-1 breaks bash with tail -f

I've run into an issue with bash-completion v1.2-1. After I tail -f a file and then press ctrl-c to stop tailing I can no longer see any text I type. My text is being entered, just not being ... echoed back. This does not happen after uninstalling 1.2-1. It also does not happen if I downgrad