From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: "Clément Pit-Claudel" <clement.pit@gmail.com>
Cc: 23925@debbugs.gnu.org, Roland Winkler <winkler@gnu.org>
Subject: bug#23925: 25.0.95; display broken when maximizing frame
Date: Wed, 19 Jun 2019 08:52:24 +0900 [thread overview]
Message-ID: <wly31ycuyv.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <787f88a7-9f0b-6d6a-43a5-b1ac967100a6@gmail.com>
On Wed, 19 Jun 2019 05:03:51 +0900,
Clément Pit-Claudel wrote:
>
> I can reproduce the issue again.
>
> On 26 Mar 2019, Yamamoto Mitsuharu wrote:
> > Does the OP still have the similar problem on master? If so, could
> > you try the patch below?
>
> The patch doesn't apply any more for me :/ Could you refresh it?
The patch has already been applied on master in a different form. It
surely fixed some problem with resizing by mouse dragging. But it
seems that another problem has been reintroduced.
> My current recipe is this:
>
> src/emacs -Q --eval "(progn (load-theme 'tango-dark t) (sleep-for 1) (setq-default initial-frame-alist '((fullscreen . maximized))) (tool-bar-mode -1) (menu-bar-mode -1))"
>
> It produces a display similar to the screenshot attached.
Thanks. I could reproduce it on Linux Mint 18.3 with GTK+3 and GTK+2
builds. On the other hand, none of --with-x-toolkit=no/athena/motif
exhibits this problem. Probably this has something to do with
GTK+-specific code.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2019-06-18 23:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 3:02 bug#23925: 25.0.95; display broken when maximizing frame Roland Winkler
2016-07-09 7:11 ` Eli Zaretskii
2016-07-09 9:45 ` Clément Pit--Claudel
2016-07-09 15:30 ` martin rudalics
2016-07-10 1:52 ` Clément Pit--Claudel
2016-07-11 9:14 ` martin rudalics
2016-07-11 17:47 ` Clément Pit--Claudel
2016-07-12 7:29 ` martin rudalics
2016-07-12 9:29 ` Clément Pit--Claudel
2016-07-13 14:58 ` Roland Winkler
2016-07-13 17:34 ` martin rudalics
2018-11-22 14:12 ` Dmitry Gutov
2018-12-11 1:40 ` Dmitry Gutov
2018-12-17 19:28 ` Clément Pit-Claudel
2019-03-26 2:12 ` YAMAMOTO Mitsuharu
2019-06-18 20:03 ` Clément Pit-Claudel
2019-06-18 21:33 ` Dmitry Gutov
2019-06-19 0:26 ` YAMAMOTO Mitsuharu
2019-06-19 1:22 ` Dmitry Gutov
2019-06-19 1:38 ` YAMAMOTO Mitsuharu
2019-06-19 1:48 ` Dmitry Gutov
2019-06-19 14:07 ` Clément Pit-Claudel
2019-06-21 0:36 ` YAMAMOTO Mitsuharu
2019-06-19 3:31 ` Roland Winkler
2019-06-18 23:52 ` YAMAMOTO Mitsuharu [this message]
2018-12-11 3:36 ` Dmitry Gutov
2018-12-11 8:49 ` Robert Pluim
2016-07-09 21:05 ` Roland Winkler
2016-07-09 9:20 ` martin rudalics
2016-07-09 17:32 ` Glenn Morris
2016-07-09 17:42 ` Eli Zaretskii
2016-07-10 1:03 ` Glenn Morris
2016-07-10 14:27 ` Eli Zaretskii
2016-07-15 15:46 ` Roland Winkler
2016-07-15 16:04 ` Eli Zaretskii
2016-07-23 17:44 ` Eli Zaretskii
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=wly31ycuyv.wl-mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=23925@debbugs.gnu.org \
--cc=clement.pit@gmail.com \
--cc=winkler@gnu.org \
/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).