From: martin rudalics <rudalics@gmx.at>
To: "Stephen Berman" <stephen.berman@gmx.net>,
"Jan Djärv" <jan.h.d@swipnet.se>
Cc: 14627@debbugs.gnu.org, Karl Brodowsky <bk1@gmx.net>
Subject: bug#14627: 24.2; Vertical frame size shrinking
Date: Fri, 13 Feb 2015 19:23:43 +0100 [thread overview]
Message-ID: <54DE412F.8050506@gmx.at> (raw)
In-Reply-To: <87k3ir3tr2.fsf@rosalinde.fritz.box>
> I've now updated and confirm that with the recipe I gave -- frame
> maximized with side by side windows, one containing an Info buffer --
> switching between the windows no longer causes the frame to shrink
> vertically. The only oddity is that when the Info buffer is selected
> there is an empty space the width of the frame one line high below the
> minibuffer.
Does this still happen with current trunk/master?
> However, there is still a shrinking problem. In KDE clicking the
> frame's (i.e. WM window's) maximize button with mouse-2 instead of
> mouse-1 maximizes the frame vertically but not horizontally. When I do
> this, then split windows (either vertically or horizontally), open an
> Info buffer in one window and switch between the windows, then the frame
> still (i.e. even with your patch) shrinks vertically by one line for
> each switch back to the Info buffer. If I drag the border of an
> unmaximized frame to make it vertically fill the desktop and repeat the
> recipe, no shrinking occurs. And if I maximize the frame horizontally
> by clicking the maximize button with mouse-3 and repeat the recipe,
> there is also no shrinking.
And this?
martin
next prev parent reply other threads:[~2015-02-13 18:23 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
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 [this message]
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=54DE412F.8050506@gmx.at \
--to=rudalics@gmx.at \
--cc=14627@debbugs.gnu.org \
--cc=bk1@gmx.net \
--cc=jan.h.d@swipnet.se \
--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.