From: "Andrew W. Nosenko" <andrew.w.nosenko@gmail.com>
To: "Michael Olson" <mwolson@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Shrinking frames as of past month
Date: Fri, 28 Mar 2008 11:33:51 +0200 [thread overview]
Message-ID: <6161f3180803280233h7b4b9f3bn9bee4c0a610928da@mail.gmail.com> (raw)
In-Reply-To: <87bq552k9h.fsf@grepfind.mwolson.org>
On Sun, Mar 23, 2008 at 11:38 PM, Michael Olson <mwolson@gnu.org> wrote:
> Jan Djärv <jan.h.d@swipnet.se> writes:
>
>
> > It seems it is a bug in Gtk+,
> > http://bugzilla.gnome.org/show_bug.cgi?id=68668
> > (http://bugzilla.gnome.org/show_bug.cgi?id=137822 explains it a bit
> > better).
> >
> > Basically because the menu bar is too large for the frame, Gtk+ sets a
> > base width that isn't a multiple of the width increment. This makes
> > the window manager shrink the text area (by 2 pixels in my case) so
> > that framw width - base width is a multiple of the width increment.
> > Then when leaving dired, we get a correct base width again. But the 2
> > pixels aren't put back, rather the window manager shrinks even more to
> > get the frame to be a multiple of the width increment.
>
> That sounds plausible. I updated the rest of my system today, and the
> problem went away, so it seems to have been the fault of GTK.
>
Could you say, which version of GTK you updated to?
Reason: I have lates stable (gtk-2.12.9) but problem didn't gone.
--
Andrew W. Nosenko <andrew.w.nosenko@gmail.com>
next prev parent reply other threads:[~2008-03-28 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 20:16 Shrinking frames as of past month Francesc Rocher
2008-03-22 11:55 ` Jan Djärv
2008-03-23 21:38 ` Michael Olson
2008-03-28 9:33 ` Andrew W. Nosenko [this message]
2008-03-28 10:35 ` Jan Djärv
2008-03-30 17:39 ` Jan Djärv
2008-03-30 19:03 ` Francesc Rocher
2008-03-31 6:21 ` Jan Djärv
-- strict thread matches above, loose matches on Subject: below --
2008-03-17 4:20 Michael Olson
2008-03-18 7:56 ` Jan Djärv
2008-03-19 1:11 ` Michael Olson
2008-03-19 16:06 ` Sam Steingold
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=6161f3180803280233h7b4b9f3bn9bee4c0a610928da@mail.gmail.com \
--to=andrew.w.nosenko@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mwolson@gnu.org \
/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.