From: Leo Liu <sdl.web@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 19355@debbugs.gnu.org
Subject: bug#19355: 25.0.50; limit the popup window height
Date: Sat, 20 Dec 2014 07:10:41 +0800 [thread overview]
Message-ID: <m2oaqzck26.fsf@gmail.com> (raw)
In-Reply-To: <54912BFF.5000401@gmx.at> (martin rudalics's message of "Wed, 17 Dec 2014 08:08:47 +0100")
On 2014-12-17 15:08 +0800, martin rudalics wrote:
> 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.)
Thanks. the harddisk of my workstation faulted, so I was moving to a new
iMac. Re-built trunk without GUI and the problem seemed to be gone.
Leo
next prev parent reply other threads:[~2014-12-19 23:10 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
2014-12-19 23:10 ` Leo Liu [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2oaqzck26.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=19355@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.