From: martin rudalics <rudalics@gmx.at>
To: Leo Liu <sdl.web@gmail.com>
Cc: 19355@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#19355: 25.0.50; limit the popup window height
Date: Wed, 17 Dec 2014 08:08:47 +0100 [thread overview]
Message-ID: <54912BFF.5000401@gmx.at> (raw)
In-Reply-To: <87ppbj14yw.fsf@gmail.com>
> I got the same thing with or without temp-buffer-resize-mode.
[...]
> The problematic case is when I am developing an elisp program in a
> window and do a completion-at-point for `(set-'. The popup takes up so
> much height that it often changes view in my editing buffer, i.e. move
> point to close to the top of the frame, push some buffer contents out of
> view etc.
[...]
I think I understand your problem but I don't understand how you can
still see it after the change I proposed. Are you sure you applied it
and recompiled the associated functions? If so, and the problem
persists, then please try to find out (1) why `fit-window-to-buffer'
apparently still gets called even if `temp-buffer-resize-mode' is off
and (2) why apparently `temp-buffer-max-width' is not observed when
`temp-buffer-resize-mode' is on. (In both cases I usually find it best
to re-evaluate the involved files, edebug `fit-window-to-buffer' /
`resize-temp-buffer-window' and get a backtrace to find out how they got
called.)
martin
next prev parent reply other threads:[~2014-12-17 7:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 1:49 bug#19355: 25.0.50; limit the popup window height Leo Liu
2014-12-12 12:45 ` martin rudalics
2014-12-12 13:05 ` Leo Liu
2014-12-12 17:19 ` martin rudalics
2014-12-13 0:17 ` Leo Liu
2014-12-13 10:21 ` martin rudalics
2014-12-13 14:41 ` Leo Liu
2014-12-13 20:03 ` martin rudalics
2014-12-14 0:37 ` Leo Liu
2014-12-14 9:03 ` martin rudalics
2014-12-17 0:43 ` Leo Liu
2014-12-17 7:08 ` martin rudalics [this message]
2014-12-19 23:10 ` Leo Liu
2014-12-25 10:35 ` martin rudalics
2014-12-25 20:01 ` Juri Linkov
2014-12-26 9:13 ` martin rudalics
2014-12-27 0:57 ` Juri Linkov
2014-12-30 10:15 ` martin rudalics
2014-12-31 0:03 ` Juri Linkov
2014-12-31 18:38 ` martin rudalics
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=54912BFF.5000401@gmx.at \
--to=rudalics@gmx.at \
--cc=19355@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=sdl.web@gmail.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 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).