Never seen that capablity be able to be disabled. And I think a core part of emacs is that it creates a *completions* buffer specifically to retain that stuff.
I get the annoyance to a degree, but in my case, the split to the buffer goes away when you finish and hit ENTER.
Now, MORE of an annoyance, but also something I've gotten away from is compilation from inside emacs, it does the same thing. What I did, and you can probably also do the same for the *completions* buffer is to hit ESC-5-2 to add another frame and have that frame showing the *completions* buffer, in my case I had it showing the *compilation* buffer and as a result when I issued compile, it did not split the frame, it instead either just did the compilation or also did the compilation, and raised the *compilation* window to the forefront, a'la switching windows. I've since stopped that. The sole benefit was that you could type the "next-error" command or key sequence and it would bring you to the file line where a compilation error was located.
That's actually a reason why the *completions* buffer, or other buffers are kept like that, for instance if you perform a grep and you get a *grep* buffer. So that you can use the "next-error" command to proceed through the results.
Long and short is that you could try opening a second frame (this then affects ALT-TAB window swapping though by adding another window to the list), and have that second frame be on the *completions* buffer. This way it won't split the window. A caveat to watch out for is if you have *completions* somewhere, but not showing in a frame, then I believe it will then split the frame; i.e. *completions* has to be the foremost buffer on "a" frame/window.
Last edited by rtmistler; 10-16-2014 at 09:53 AM.
|