[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: al
From: |
Stefan Monnier |
Subject: |
bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*? |
Date: |
Mon, 28 Mar 2011 21:05:48 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
> Should be able to set it at any time and have it take effect (not be
> wiped out by `with-output-to-temp-buffer'. Anyway, it's clear we
> don't agree. The simple solution (trivial in this case) is for me to
> just roll my own and forget about using `scroll-other-window(-down)'
> and `minibuffer-scroll-window', since they are essentially hard-coded
> during completion.
Here's my question:
given that we want (by default) scroll-other-window to scroll the
*Completions* buffer when called from the minibuffer and *Completions*
has been displayed, how else would you implement this in a way that
also satisfies your needs?
IOW send us some kind of patch to the Emacs code that does not change
the current default behavior, but makes it flexible in the way
you expect.
Stefan
- bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*?, Drew Adams, 2011/03/27
- bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*?, Stefan Monnier, 2011/03/28
- bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*?, Drew Adams, 2011/03/29
- bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*?, martin rudalics, 2011/03/29
- bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*?, Drew Adams, 2011/03/29