Bug#479375: asterisk console screws up terminal subtly when exited with ctrl-c

[Tzafrir Cohen]

On Sun, May 04, 2008 at 02:56:49PM +0100, martin f krafft wrote:
> Package: asterisk
> Version: 1.4.11~dfsg-3.4652
> Severity: minor
> 
> Exiting an asterisk -r session with ctrl-c leaves the terminal
> slightly messed up. When normally, ctrl-d exits the shell, it now
> does tab completion, as if something's already on the buffer.
> 
> wall:~# asterisk -r
> [...]
> wall*CLI>
> *** CTRL-C pressed here ***
> wall:~#
> *** CTRL-D pressed here***
> zsh: do you wish to see all 1670 possibilities (835 lines)? n

That's a nice one. This seems to be triggered by the combination of zsh
and asterisk. It is cleared by issuing 'stty sane'.

I tried comparing the output of 'stty -a' at the following:

1. Clear start ("sane")
2. Starting Asterisk from zsh and pressing ctrl-C ("zshbad")
3. Starting Asterisk from bash and pressing ctrl-C ("bashbad").

No noticable differences between "sane" and "bashbad". The differences
between "sane" and "zshbad" are:

	sane	zshbad
	----    ------
eof     ^D      <undef>	
rprnt   ^R      <undef>
werase  ^W      <undef>	
lnext   ^V      <undef>
      -inlcr    inlcr
      iexten	-iexten
      echok     -echok

I figure this issue is triggered by ^D not defined.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir