Path: utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!mailrus!eecae!cps3xx!rang
From: rang@cpsin3.cps.msu.edu (Anton Rang)
Newsgroups: gnu.emacs.bug
Subject: Re: ^X-O inside minibuffer
Message-ID: <1536@cps3xx.UUCP>
Date: 16 Jan 89 14:19:00 GMT
References: <8901160850.AA03044@total.ai.mit.edu>
Sender: usenet@cps3xx.UUCP
Reply-To: rang@cpswh.cps.msu.edu (Anton Rang)
Distribution: gnu
Organization: Michigan State University, Computer Science Dept.
Lines: 21
In-reply-to: klotz@WHEATIES.AI.MIT.EDU's message of 16 Jan 89 08:50:06 GMT

In article <8901160850.AA03044@total.ai.mit.edu> klotz@WHEATIES.AI.MIT.EDU (Leigh L. Klotz) writes:

>I finally figured out the source of a bizzare annoyance.
>
>If you do ^X-O inside a minibuffer, you will get into
>a bizzare mode where the minibuffer prompt (Find File,
>Switch to Buffer, whatever) will keep being redisplayed
>in the echo area [ ... ]
>
>Maybe ^X-O should be disabled inside the minibuffer,
>just as ^X-2 is.

  I disagree.  It's useful to be able to go into another window while
doing a find-file, for example, or an eval.  It gives you an easy way
to scroll through the *Completions* buffer, for example.  In 'eval',
you can copy a Lisp expression and then yank it in the minibuffer.

+---------------------------+------------------------+----------------------+
| Anton Rang (grad student) | "UNIX: Just Say No!"   | "Do worry...be SAD!" |
| Michigan State University | rang@cpswh.cps.msu.edu |                      |
+---------------------------+------------------------+----------------------+