unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Robert Pluim <rpluim@gmail.com>
Cc: 31745@debbugs.gnu.org, 刘力铭 <mark.liu.li.ming@foxmail.com>
Subject: bug#31745: 回复: bug#31745: 回复:回复:Re: 回复:bug#31745: Frame's bug whenwindow-system
Date: Thu, 28 Jun 2018 14:25:20 +0200	[thread overview]
Message-ID: <5B34D3B0.3060302@gmx.at> (raw)
In-Reply-To: <87tvpnnuuw.fsf@gmail.com>

 >> (modify-frame-parameters nil '((left . 0) (top . 0) (width . 130) (height . 56)))
 >>
 >
 > That does nothing, but the following resizes the frame:
 >
 > (modify-frame-parameters nil '((left . 0) (top . 0) (width . 100) (height . 48)))
 >
 > And has done the right thing:
 >
 > (frame-parameter nil 'height) => 48
 > (frame-parameter nil 'width) => 100

Looks like the missing link.  If your window manager refuses to resize
the frame, it probably decides that it would not fit on the screen.
Please increase separately from 48 and 100 till you find the
problematic value and compare it against your workspace size.

 >> What give (frame-pixel-width) and (frame-pixel-height) for this frame
 >> in the bad and good states?
 >>
 >
 > Bad:
 >
 > (frame-pixel-width) => 1849
 > (frame-pixel-height) => 1680
 >
 > Good:
 >
 > (frame-pixel-width) => 1849
 > (frame-pixel-height) => 1680

This looks like our bad.  Somehow we decide that the window manager
will comply and set the values we asked for.  Do these values also
occur with emacs -Q followed by

(modify-frame-parameters nil '((left . 0) (top . 0) (width . 130) (height . 56)))

I suppose not since otherwise you would have probably told me so.

 >> Can you try with another toolkit or X without any toolkit so we can
 >> tell whether this is GTK or window manager specific?
 >
 > --with-x-toolkit={none,lucid} both work fine (although you can see the
 >    modeline of the frame appear as if it were 80x36, and then it
 >    resizes correctly to 130x56).

This implies that the bug is somewhere in our interception of X
messages and letting GTK not see them (otherwise GTK should have
reported an error).  However, it contradicts the assumption that the
window manager refuses to resize our frame since otherwise it would
have done so for the Lucid build too.  Rather it seems that GTK itself
decides that the frame is too large to fit on the screen.  But without
signalling an error?

martin





  reply	other threads:[~2018-06-28 12:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_31247D97CC59228818C55E91FB6828E17407@qq.com>
2018-06-08 11:33 ` bug#31745: 回复: bug#31745: 回复:Re: 回复:bug#31745: Frame's bug whenwindow-system Robert Pluim
     [not found]   ` <tencent_77BD98CBDECAFB6E2884F40BFD81CC292207@qq.com>
2018-06-08 12:43     ` bug#31745: 回复: bug#31745: 回复:回复:Re: " Robert Pluim
2018-06-21 11:41       ` Noam Postavsky
2018-06-21 11:59         ` Robert Pluim
2018-06-22  8:56       ` martin rudalics
2018-06-22 14:44         ` Robert Pluim
2018-06-23  8:40           ` martin rudalics
2018-06-27  9:01             ` Robert Pluim
2018-06-28  8:02               ` martin rudalics
2018-06-28  8:25                 ` Robert Pluim
2018-06-28  8:33                   ` martin rudalics
2018-06-28  9:06                     ` Robert Pluim
2018-06-28 12:25                       ` martin rudalics [this message]
2018-06-28 14:15                         ` Robert Pluim
2018-06-29  8:42                           ` martin rudalics
2018-06-29 11:57                             ` Robert Pluim
2018-06-30  8:34                               ` martin rudalics
2018-06-30  9:13                                 ` Robert Pluim
2018-07-01  9:02                                   ` martin rudalics
2018-07-02  4:58                                     ` bug#31745: �ظ��� bug#31745: �ظ����ظ���Re: �ظ���bug#31745: " �����
2018-07-02 14:31                                     ` bug#31745: 回复: bug#31745: 回复:回复:Re: 回复:bug#31745: " Robert Pluim
2018-07-02 15:26                                       ` bug#31745: bug#31745: �ظ����ظ����ظ���Re: �ظ���bug#31745: Frame'sbug whenwindow-system �����
2022-04-28 10:42                                         ` bug#31745: default-frame-alist sizing parameters set in ~/.emacs are not applied correctly Lars Ingebrigtsen
2022-05-26 12:49                                           ` Lars Ingebrigtsen
2018-06-22 15:30         ` bug#31745: �ظ��� bug#31745: �ظ��� bug#31745: �ظ����ظ���Re: �ظ���bug#31745: Frame's bug whenwindow-system �����
2018-06-23  8:40           ` bug#31745: 回复: bug#31745: 回复: bug#31745: 回复:回复:Re: 回复:bug#31745: " martin rudalics
2018-06-23 11:50             ` bug#31745: �ظ��� bug#31745: �ظ��� bug#31745: �ظ����ظ���Re: �ظ���bug#31745: " �����
2018-06-27  7:34               ` bug#31745: 回复: bug#31745: 回复: bug#31745: 回复:回复:Re: 回复:bug#31745: " martin rudalics
2018-06-27  9:13                 ` Robert Pluim

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=5B34D3B0.3060302@gmx.at \
    --to=rudalics@gmx.at \
    --cc=31745@debbugs.gnu.org \
    --cc=mark.liu.li.ming@foxmail.com \
    --cc=rpluim@gmail.com \
    /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).