From: martin rudalics <rudalics@gmx.at>
To: arne.babenhauserheide@kit.edu
Cc: "13469@debbugs.gnu.org" <13469@debbugs.gnu.org>,
"arne_bab@web.de" <arne_bab@web.de>
Subject: bug#13469: 24.2; emacs has a tiny frame, when I embed it in a kmail text field via xembed (--parent-id %w)
Date: Thu, 21 Mar 2013 12:37:55 +0100 [thread overview]
Message-ID: <514AF113.8040905@gmx.at> (raw)
In-Reply-To: <514AE793.8080303@kit.edu>
>>> Especially strange is that it works with emacs -Q --basic-display.
>> The --basic-display disables menu bar and tool bar, and also disables
>> blinking cursor. Maybe the absent menu and tool bar somehow affect
>> this, when you resize the qxembed-window?
>
> When I disable the menu bar, the frame is a bit bigger even without
> --basic-display. It still resizes to the tiny size, though.
Did you also try with a disabled toolbar?
> I just found a much easier way to reproduce it:
>
> Run emacs with --parent-id <random number>
>
> Then click with the mouse on the minibuffer. With menubar, it gets
> really tiny, without menubar it resizes to a bigger size (~4 times as
> wide
... high, I presume ...
> as the small size), but when I click the minibuffer it emacs starts
> to flicker and to resize repeatedly.
... how does it resize and how do you observe that ?
> The flickering stops, when I call
> async-shell-command but starts again once I hit C-g to leave the minibuffer.
Does it flicker/resize when you enter the minibuffer or when you leave
it?
>> I suggest to put a breakpoint in change_frame_size,
change_frame_size_1 is better, where it does block_input () so you avoid
delayed and not-changing-anything calls.
> and see who calls
>> it with such a small frame size.
>
> I get something like this:
In all these calls can you see something in newheight that reflects the
size change you requested?
martin
next prev parent reply other threads:[~2013-03-21 11:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 23:52 bug#13469: 24.2; emacs has a tiny frame, when I embed it in a kmail text field via xembed (--parent-id %w) Arne Babenhauserheide
2013-03-19 10:39 ` Arne Babenhauserheide (IMK)
2013-03-20 3:46 ` Eli Zaretskii
[not found] ` <51497A90.7070901@kit.edu>
2013-03-20 19:26 ` Eli Zaretskii
2013-03-21 10:57 ` Arne Babenhauserheide (IMK)
2013-03-21 11:37 ` martin rudalics [this message]
2013-03-21 17:36 ` Eli Zaretskii
2013-03-21 20:23 ` Arne Babenhauserheide
2013-03-22 7:00 ` Jan Djärv
2022-02-05 23:56 ` Lars Ingebrigtsen
2022-03-06 2:36 ` Lars Ingebrigtsen
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=514AF113.8040905@gmx.at \
--to=rudalics@gmx.at \
--cc=13469@debbugs.gnu.org \
--cc=arne.babenhauserheide@kit.edu \
--cc=arne_bab@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).