From: Trey Jackson <bigfaceworm@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: minibuffer-scroll-window question
Date: Tue, 26 May 2009 10:25:29 -0700 [thread overview]
Message-ID: <198e25e10905261025h65ea6a2avc79cbfe7d04b7521@mail.gmail.com> (raw)
In-Reply-To: <jwvd49xs06h.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Thanks for the explanation. The alternative worked well.
Any chance the doc string for minibuffer-scroll-window could be updated to
reflect that it's for
internal use only, or at least that it's for read-only access?
thanks,
TJ
On Mon, May 25, 2009 at 7:58 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> > (defun my-minibuffer-setup-hook ()
> > "try to force the scroll window to be the bottom-left window in the
> > current frame"
> > (setq minibuffer-scroll-window (window-at 0 (- (frame-height) 2))))
> > (add-hook 'minibuffer-setup-hook 'my-minibuffer-setup-hook)
>
> > However, in minibuf.c, the defun 'minibuffer-complete sets the
> > minibuf_scroll_window variable to nil.
>
> > So, my question is, how and when can this variable be meaningfully used
> by
> > an end user? Should my hook have worked (i.e. this behavior is a bug)?
>
> It was not intended to be set by the end user, it's supposed to be
> *read* instead (so you can't decide where to put the "scroll window"
> but you can figure out which window it is).
>
> To tell you the truth, I think it's largely unsatisfactory, not only
> because you can't do what you want, but also because that variable
> can point to different buffers in different cases.
>
> In your case, which buffer do you expect to see in that scroll window?
> The *Completions* buffer? In that case, maybe you'll be better off
> using special-display-buffer-names to control how/where *Completions*
> get displayed.
>
>
> Stefan
>
--
Trey Jackson
bigfaceworm@gmail.com
"Like any truly useful program, `hello' contains a built-in mail reader."
-- GNU's Bulletin, July 1996
[-- Attachment #2: Type: text/html, Size: 2311 bytes --]
prev parent reply other threads:[~2009-05-26 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 2:39 minibuffer-scroll-window question Trey Jackson
2009-05-25 14:58 ` Stefan Monnier
2009-05-26 17:25 ` Trey Jackson [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=198e25e10905261025h65ea6a2avc79cbfe7d04b7521@mail.gmail.com \
--to=bigfaceworm@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).