Date: Tue, 20 Oct 1998 22:12:45 -0600 From: Brett Glass <brett@lariat.org> To: "Jeffrey J. Mountin" <jeff-ml@mountin.net>, "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>, "Studded" <Studded@gorean.org> Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG> Subject: Re: No terminal echo after certain commands Message-ID: <4.1.19981020220950.06c1aca0@mail.lariat.org> In-Reply-To: <3.0.3.32.19981020222556.01047304@207.227.119.2> References: <4.1.19981020191142.06b355b0@mail.lariat.org> <199810210058.UAA30643@laker.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:25 PM 10/20/98 -0500, Jeffrey J. Mountin wrote: >By now one should have found using 1 keystroke "q" easier than a >combination "CTL-c". </facetious> Perhaps. But ^C is programmed into many folks' fingertips. ESPECIALLY UNIX hackers. It's the correct way out of many, MANY things. >Doug's point is along line that only a novice would try this and hopefully >read the man page and learn about the "q" exit command. Sometimes I do use "q". However, using ^C should be acceptable as well. Restoring echo on the terminal is not a time-consuming operation or one that's going to fail unless the system is crashing. >At least it doesn't want escape-enter. ;) That's a minor relief.... ;-) --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19981020220950.06c1aca0>