From: Eli Zaretskii <eliz@gnu.org>
To: arne.babenhauserheide@kit.edu
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: Wed, 20 Mar 2013 05:46:16 +0200 [thread overview]
Message-ID: <837gl220on.fsf@gnu.org> (raw)
In-Reply-To: <5148405C.2000808@kit.edu>
> Date: Tue, 19 Mar 2013 11:39:24 +0100
> From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@kit.edu>
>
> I can reproduce this bug with a simple qxembed frame. Steps:
>
>
> (1) Get qxembed-emacs:
>
> https://bitbucket.org/ArneBab/kembed-emacs/src/71b958b3f737a62987dfc7cd39eb3edcb02308b2/qxembed-emacs.py
> hg clone https://bitbucket.org/ArneBab/kembed-emacs
>
> (2) run ./qxembed-emacs.py
>
> (3) resize the qxembed-window.
>
> (4) do the same with ./qxembed-emacs.py --basic
> this opens emacs with -Q --basic-display
>
>
> For me, (3) has an embedded emacs which shrinks down instantly to maybe
> 5 chars after releasing the window.
>
> With (4) the embedded emacs is adjusted to the window size after the
> first resize and then stays embedded correctly. But it looks odd due to
> the --basic-display.
Is there any evidence that this is an Emacs bug, and not a bug in
qxembed-emacs.py? Can you reproduce something similar with just
Emacs?
next prev parent reply other threads:[~2013-03-20 3:46 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 [this message]
[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
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=837gl220on.fsf@gnu.org \
--to=eliz@gnu.org \
--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).