From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8358@debbugs.gnu.org
Subject: bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*?
Date: Mon, 28 Mar 2011 21:05:48 -0400 [thread overview]
Message-ID: <jwvd3la91w8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E9218D2492C140FAA2E2ED0194B888A1@us.oracle.com> (Drew Adams's message of "Mon, 28 Mar 2011 13:00:55 -0700")
> 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
next prev parent reply other threads:[~2011-03-29 1:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 22:03 bug#8358: 24.0.50; `minibuffer-scroll-window' with active minibuffer: always *Completions*? Drew Adams
2011-03-28 6:34 ` martin rudalics
2011-03-28 13:44 ` Drew Adams
2011-03-28 15:01 ` martin rudalics
2011-03-28 16:22 ` Drew Adams
2011-03-28 18:51 ` martin rudalics
2011-03-28 20:00 ` Drew Adams
2011-03-29 1:05 ` Stefan Monnier [this message]
2022-02-13 9:58 ` Lars Ingebrigtsen
2011-03-28 15:07 ` Stefan Monnier
2011-03-29 4:13 ` Drew Adams
2011-03-29 8:54 ` martin rudalics
2011-03-29 14:22 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvd3la91w8.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=8358@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.