From: James Nguyen <ja.nguyen@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 24285@debbugs.gnu.org
Subject: bug#24285: 25.1; Overlay doesn't work as expected when more than one frame exists
Date: Mon, 22 Aug 2016 09:29:11 -0700 [thread overview]
Message-ID: <80193592-896D-4250-ADDE-6F1837E105DF@gmail.com> (raw)
In-Reply-To: <87k2f8om46.fsf@web.de>
The expected behavior for me is that the minibuffer resizes regardless of how many frames are up.
When the frame count is 1, the minibuffer resizes as expected but adding a new frame causes the resizing to not show up (on either frame).
Closing one frame (going back to frame count of 1) lets me see the expected resizing.
> On Aug 22, 2016, at 8:32 AM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> What exactly do you see then? All I see is that the minibuffer
>> doesn't get resized, but once I move the cursor there, I see the
>> entire overlay. Is that what you see?
>
> What I see can be interpreted in that way, yes.
>
> BTW, AFAIR the other recipe I posted is also related to mini-window
> resizing.
>
>
> Michael.
next prev parent reply other threads:[~2016-08-22 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 23:10 bug#24285: 25.1; Overlay doesn't work as expected when more than one frame exists James Nguyen
2016-08-22 8:11 ` martin rudalics
2016-08-22 15:22 ` Michael Heerdegen
2016-08-22 15:26 ` Eli Zaretskii
2016-08-22 15:32 ` Michael Heerdegen
2016-08-22 16:29 ` James Nguyen [this message]
2016-08-22 17:21 ` Eli Zaretskii
2016-08-22 18:07 ` James Nguyen
2016-08-22 18:24 ` Eli Zaretskii
2016-08-23 1:43 ` James Nguyen
2016-08-23 2:36 ` Eli Zaretskii
2016-08-22 15:29 ` Michael Heerdegen
2016-08-22 17:23 ` Eli Zaretskii
2016-08-23 15:50 ` Michael Heerdegen
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=80193592-896D-4250-ADDE-6F1837E105DF@gmail.com \
--to=ja.nguyen@gmail.com \
--cc=24285@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).