all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bk1@gmx.net, stephen.berman@gmx.net, 14627@debbugs.gnu.org
Subject: bug#14627: 24.2; Vertical frame size shrinking
Date: Fri, 23 Aug 2013 18:22:16 +0200	[thread overview]
Message-ID: <8202DFA0-0B3F-40FC-8773-FC56F965A2D5@swipnet.se> (raw)
In-Reply-To: <83ioywirwx.fsf@gnu.org>

Hello.

23 aug 2013 kl. 13:10 skrev Eli Zaretskii <eliz@gnu.org>:

>> Date: Fri, 23 Aug 2013 12:46:01 +0200
>> From: martin rudalics <rudalics@gmx.at>
>> CC: stephen.berman@gmx.net, 14627@debbugs.gnu.org, bk1@gmx.net
>> 
>>>> The OP uses cyrillic and Stephen invokes Info, could these give a
>>>> clue?
>>> 
>>> I don't think so, certainly not with Info.
>> 
>> Info has a special toolbar.
> 
> Right, but we already talked about that: only image sizes can change
> the toolbar's size.

In 99 cases out of 100 these cases are due to either the inherent race in wm_size_hints or bugs in the window manager.  In this case it is probably the latter.

I suspect the tool bar changes for the OP.  That makes Emacs send new wm_size_hints to the window manager, telling it what the base- and increment sizes are.  If the tool bar changes, the base size changes (the size not counted against resize increments, i.e. font size).  Normally a window manager shall then make sure Emacs frame has the appropriate size, i.e.

    height = base_y + inc_y * n

where n is an integer.

But in this case the frame is maximized, so the window manager should do nothing, like all other window managers.

A possible workaround is not to update size hints when Emacs is maximized or fullscreen.

	Jan D.






  reply	other threads:[~2013-08-23 16:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 14:22 bug#14627: 24.2; Vertical frame size shrinking Karl Brodowsky
2013-08-19 18:56 ` Jan Djärv
2013-08-19 19:15   ` Jan Djärv
2013-08-22 11:32   ` Stephen Berman
2013-08-22 11:51     ` Stephen Berman
2013-08-22 11:59       ` Stephen Berman
2013-08-22 12:15     ` martin rudalics
2013-08-22 12:25       ` Stephen Berman
2013-08-23  7:10         ` martin rudalics
2013-08-23  8:20           ` Eli Zaretskii
2013-08-23  8:55             ` martin rudalics
2013-08-23  9:25               ` Eli Zaretskii
2013-08-23 10:21                 ` martin rudalics
2013-08-23 10:33                   ` Eli Zaretskii
2013-08-23 10:46                     ` martin rudalics
2013-08-23 11:10                       ` Eli Zaretskii
2013-08-23 16:22                         ` Jan Djärv [this message]
2013-08-23 17:39                           ` Eli Zaretskii
2013-08-23 17:55                             ` martin rudalics
2013-08-23 17:58                               ` Jan Djärv
2013-08-23 18:06                                 ` martin rudalics
2013-08-23 18:02                               ` Karl Brodowsky
2013-08-23 18:06                                 ` martin rudalics
2013-08-23 18:14                                   ` Karl Brodowsky
2013-08-24  8:55                                     ` martin rudalics
2013-08-23 17:55                           ` Karl Brodowsky
2013-08-24  8:45                             ` Jan Djärv
2013-09-08 21:09                               ` Stephen Berman
2013-09-09 12:00                                 ` martin rudalics
2013-09-09 12:23                                   ` Stephen Berman
2015-02-13 18:23                                 ` martin rudalics
2015-02-15 13:38                                   ` Stephen Berman
2015-02-16 18:35                                     ` martin rudalics

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8202DFA0-0B3F-40FC-8773-FC56F965A2D5@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=14627@debbugs.gnu.org \
    --cc=bk1@gmx.net \
    --cc=eliz@gnu.org \
    --cc=stephen.berman@gmx.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.