From owner-freebsd-questions Thu Sep 25 04:46:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA12372 for questions-outgoing; Thu, 25 Sep 1997 04:46:29 -0700 (PDT) Received: from BIGFUN.vwcom.com (BIGFUN.vwcom.com [151.197.101.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA12367 for ; Thu, 25 Sep 1997 04:46:26 -0700 (PDT) Received: from WillsCreek.COM (gw.willscreek.com [151.197.101.46]) by BIGFUN.vwcom.com (8.8.6/8.8.6) with ESMTP id HAA11083 for ; Thu, 25 Sep 1997 07:41:43 -0400 (EDT) Received: from current.willscreek.com (current.willscreek.com [172.16.87.1]) by WillsCreek.COM (8.8.5/8.8.5) with ESMTP id HAA23670 for ; Thu, 25 Sep 1997 07:46:19 -0400 (EDT) Received: (from bmc@localhost) by current.willscreek.com (8.8.5/8.8.5) id HAA01635; Thu, 25 Sep 1997 07:46:18 -0400 (EDT) Date: Thu, 25 Sep 1997 07:46:18 -0400 (EDT) Message-Id: <199709251146.HAA01635@current.willscreek.com> From: Brian Clapper MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: questions@FreeBSD.ORG Subject: Re: Strange EMACS / BASH2 occurrence In-Reply-To: <115215185@toto.iv> X-Mailer: VM 6.23 under Emacs 19.34.1 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Don Wilde wrote: > I had a strange thing happen to me a little while ago on my P6 > webserver. I use the new BASH2 shell from the 2.2.2 CD, and the EMACS > (19.34?) that comes on the same CD, and something strange happened to > me. I do have the X libraries installed, and I've been running fine > (console mode, no X), but I got trapped in a wierd command history > buffer mode and couldn't get out except with the ALT-F-key terminals. I > could scroll back in a sort of 'history buffer' that included several > EMACS sessions (as though screen captures) and a number of commands at > the shell level, but I couldn't for the life of me get out. Can't > reproduce it, don't want to, just want to know what NOT to do, as I > almost lost mucho work... Thank you, #*#!!! > Anybody seen this? TIA! Were you on one of the console virtual terminals? If so, you probably hit the SCROLL LOCK key, which takes the virtual terminal out of input mode and into a history-scrolling mode. Hitting SCROLL LOCK again toggles back to input mode. Try it; see if it matches what you experienced. ----- Brian Clapper, bmc@WillsCreek.COM, http://WWW.WillsCreek.COM/ All progress is based upon a universal innate desire on the part of every organism to live beyond its income. -- Samuel Butler