Date: Thu, 10 Mar 2016 07:25:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 207873] csh(1) terminates on CTRL-C Message-ID: <bug-207873-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207873 Bug ID: 207873 Summary: csh(1) terminates on CTRL-C Product: Base System Version: 10.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: olivier.nicole@cs.ait.ac.th csh(1) will close when pressing CTRL-C. This is a very unwelcome behaviour because I switch between Windows and FreeBSD environment all the time and in Windows, CTRL-C is the copy command. Here is an example of session: banyan<on>41: csh -f % CTRL-C % CTRL-C % CTRL-C % echo oo bar oo bar % CTRL-C % CTRL-C=20 % CTRL-C % uname -a FreeBSD banyan.cs.ait.ac.th 10.2-RELEASE-p12 FreeBSD 10.2-RELEASE-p12 #2 r295233: Thu Feb 18 13:42:07 ICT 2016=20=20=20=20 root@banyan.cs.ait.ac.th:/usr/obj/usr/src/sys/CSIM amd64 % CTRL-C banyan<on>42:=20 I launch a new C Shell, without loading any rc confifiguration. CTRL-C is inactive as long as I have not executed a command (shell internal command a= re not concerned). As soon as I have executed one command, for example uname, CTRL-C will close the shell. I have several amd64 systems exhibiting the same behaviour (one 10.2-RELEASE-p10 is immune), while on i386, I have no problem, CTRL-C does nothing in csh(1) (except one 10.2-RELEASE-p10). I have repeated the same behaviour on the console and in xterm. It seems that this appeared with the latest security patches, around the new year, but it is only recently that I finally noticed the pattern. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207873-8>