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: Sun, 01 Jul 2018 11:02:00 +0200 [thread overview]
Message-ID: <5B389888.2060003@gmx.at> (raw)
In-Reply-To: <87in60ab7p.fsf@gmail.com>
>>From the *scratch* buffer, after emacs has finished displaying the
> initial frame.
Then let's ignore the initial frame behavior for the moment and
concentrate on this. We have to find out the reason why the window
manager might refuse to resize our frame as requested. There can't be
many of them. Either the size wrt to the frame's position is too
large. This could be verified by finding a corresponding threshold
value beyond which the frame cannot be resized. Or the value
specified does not result in an integral multiple of character sizes.
This could be verified by setting 'frame-resize-pixelwise' to t. I
can't see any other reason. Can you?
In either case it would be interesting to have a look at the sources
of the window manager you use.
martin
next prev parent reply other threads:[~2018-07-01 9:02 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
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 [this message]
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=5B389888.2060003@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).