On Saturday, March 1, 2014, martin rudalics &lt;<a href="mailto:rudalics@gmx.at">rudalics@gmx.at</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&gt; I just posted this setq line as a workaround. And why does it break? Because if you set it then C-M-v will always try to scroll *Completions* and not regular other-window buffer which is useful sometimes (e.g. while using help, an approach mentioned even in tutorial).<br>

<br>
So it seems there are two ways to tackle this problem:<br>
<br>
(1) Kill the *Completions* buffer when we&#39;re done so it won&#39;t be<br>
    inadvertently displayed by `other-window-for-scrolling&#39;.</blockquote><div><br></div><div>How is this supposed to work?</div><div>The problem is _during_ the Completions buffer is shown, when we&#39;re hitting Tab, not when we&#39;re done. Besides its window is usually closed automatically. Killing the buffer won&#39;t make the scroll-other-window work the usuall way.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(2) Bind `other-window-scroll-buffer&#39; temporarily only as long as the<br>
    *Completions* buffer is shown.</blockquote><div><br></div><div>This would work I imagine. But don&#39;t do this in general when the Completions buffer is shown, but only when we use autocomplete functionality with Tab _and_ the buffer is shown.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
martin<br>
</blockquote><br><br>-- <br>Regards<br>Havner<br><br>