[Bash-completion-devel] Expect buffering fixes

Crestez Dan Leonard cdleonard at gmail.com
Tue Feb 23 21:09:03 UTC 2010


On Tue, 2010-02-23 at 21:49 +0100, Freddy Vulto wrote: 
> On 100223 19:28, Ville Skyttä wrote:
> > Confirmed.  Ditto with bash 3.2.25.
> 
> I notice the difference when just typing a ^C.  On bash >= 4 it is echoed
> as ^C, but on bash-3 it is echoed as a newline.  I think I'll ask the
> bug-bash mailing list.  If we could just make bash-3 echo the "^C"...
It seems that bash versions < 4 don't echo ^C for some reason. I ran
stty -a to check if any terminal settings were different but nothing
showed up. I know very little about how ttys work and don't particularly
want to dig at this.

One solution would be to send a string like 'sync123' with a random
number before the ^C. Matching that would be easy and reliable; combined
with a BASH_VERSION check for ^C.




More information about the Bash-completion-devel mailing list