unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 14627@debbugs.gnu.org, bk1@gmx.net, stephen.berman@gmx.net
Subject: bug#14627: 24.2; Vertical frame size shrinking
Date: Fri, 23 Aug 2013 11:20:34 +0300	[thread overview]
Message-ID: <83ob8oizsd.fsf@gnu.org> (raw)
In-Reply-To: <52170AD8.8010001@gmx.at>

> Date: Fri, 23 Aug 2013 09:10:16 +0200
> From: martin rudalics <rudalics@gmx.at>
> Cc: 14627@debbugs.gnu.org, Karl Brodowsky <bk1@gmx.net>
> 
> I think we have two bugs here:

I think we have three.

> (1) A maximized frame should never shrink due to a font change.
> 
> (2) There seems to be a rounding error present which always chooses to
>      shrink the frame when changing the toolbar size.

 (3) Why does a frame change its size when one clicks on it?





  reply	other threads:[~2013-08-23  8:20 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 [this message]
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
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

  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=83ob8oizsd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=14627@debbugs.gnu.org \
    --cc=bk1@gmx.net \
    --cc=rudalics@gmx.at \
    --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 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).