From: Eli Zaretskii <eliz@gnu.org>
To: arne.babenhauserheide@kit.edu, "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 13469@debbugs.gnu.org, 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 19:36:27 +0200 [thread overview]
Message-ID: <838v5gzmck.fsf@gnu.org> (raw)
In-Reply-To: <514AE793.8080303@kit.edu>
> Date: Thu, 21 Mar 2013 11:57:23 +0100
> From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@kit.edu>
> CC: "13469@debbugs.gnu.org" <13469@debbugs.gnu.org>, "arne_bab@web.de"
> <arne_bab@web.de>
>
> I just found a much easier way to reproduce it:
>
> Run emacs with --parent-id <random number>
So it looks like something specific to using the XEmbed protocol, I
guess.
> A backtrace after clicking the minibuffer (which triggers a resize)
> looks like this (without menubar):
>
> Breakpoint 1, change_frame_size (f=f@entry=0x104b4b0,
> newheight=newheight@entry=5, newwidth=newwidth@entry=21,
> pretend=pretend@entry=0, delay=delay@entry=1,
> safe=safe@entry=0) at dispnew.c:5726
> 5726 in dispnew.c
> (gdb) backtrace
> #0 change_frame_size (f=f@entry=0x104b4b0, newheight=newheight@entry=5,
> newwidth=newwidth@entry=21, pretend=pretend@entry=0,
> delay=delay@entry=1, safe=safe@entry=0)
> at dispnew.c:5726
> #1 0x00000000004ed1c8 in xg_frame_resized (f=0x104b4b0, pixelwidth=200,
> pixelheight=75) at gtkutil.c:888
> #2 0x00000000004c3056 in handle_one_xevent
> (dpyinfo=dpyinfo@entry=0x101a3f0,
> eventptr=eventptr@entry=0x7fffffffc360, finish=finish@entry=0xaee010
> <current_finish>,
> hold_quit=0x7fffffffc720) at xterm.c:6813
> #3 0x00000000004c3a34 in event_handler_gdk (gxev=0x7fffffffc360,
> ev=<optimized out>, data=<optimized out>) at xterm.c:5834
> #4 0x00007ffff7543d52 in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
> #5 0x00007ffff75454f8 in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
> #6 0x00007ffff754557e in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
> #7 0x00007ffff68c0883 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
This looks like GTK instructed us to resize ourselves to 200x75
pixels, which was quite reasonably translated to 21x5 characters.
Sounds like a good time for some GTK expert (Jan?) to chime in and
help us out.
next prev parent reply other threads:[~2013-03-21 17:36 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
2013-03-21 17:36 ` Eli Zaretskii [this message]
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=838v5gzmck.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13469@debbugs.gnu.org \
--cc=arne.babenhauserheide@kit.edu \
--cc=arne_bab@web.de \
--cc=jan.h.d@swipnet.se \
/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).