drw@culdev1.UUCP (Dale Worley) (10/13/87)
Ahhh, yes. The trick is that you must not actually finish the process of entering the command name in M-x, because when you do, the *Completions* buffer is scrapped. You are forbidden to use C-x b to switch to that buffer, because you are already in the minibuffer, and C-x b prompts in the minibuffer. The solution is to use C-x o to switch to the window that *Completions* is in. But remember, you are still inside of the M-x prompting process, and will someday have to finish it or abort it. (But you can still use minibuffer-using commands, since the cursor isn't in the minibuffer!) Dale -- Dale Worley Cullinet Software ARPA: culdev1!drw@eddie.mit.edu UUCP: ...!seismo!harvard!mit-eddie!culdev1!drw Give me money or kill me! Exercise your childishness -- remember, we are all 10 in some base.
rlk@think.COM (Robert Krawitz) (10/13/87)
In article <1644@culdev1.UUCP> drw@culdev1.UUCP (Dale Worley) writes:
]Ahhh, yes. The trick is that you must not actually finish the process
]of entering the command name in M-x, because when you do, the
]*Completions* buffer is scrapped.
This is a common misconception. The buffer is not named
"*Completions*", but rather " *Completions*", which effectively makes
it invisible. You can switch to this buffer by typing a ' *C<tab>'
(or however many characters you need to complete) to the prompt from
C-xb. Just be careful you don't hit the minibuffer (named
*Minibuf-0* or the like) or you'll get very badly screwed (core
dump).
cca >>>>>>>>>> |
harvard >>>>>> |
bloom-beacon > |think!rlk Robert Krawitz <rlk@think.com>
rutgers >>>>>> |
ihnp4 >>>>>>>> .