From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: Mini-window glitch with GTK
Date: Mon, 21 Jan 2013 18:29:27 +0100 [thread overview]
Message-ID: <CAH8Pv0hz=XySKVMTo5OzqMRaG1g7cL8WQ5XvbbKFfrYvQ884ig@mail.gmail.com> (raw)
In-Reply-To: <834niapi7s.fsf@gnu.org>
>> > On Fedora 18 with GTK 3.6.4, height of the minibuffer window looks too large
>> > immediately after startup (screenshot 1), but shrinks to normal after first
>> > input comes (screenshot 2). The problem is easily visible with ./src/emacs
>> > -Q,
>> > but doesn't appear with ./src/emacs -Q --execute '(tool-bar-mode 0)'.
>>
>> This same problem occurs on MS-Windows. When the frame is maximized,
>> the remnant vertical space is put at the very bottom, instead of using
>> it to show more content on the main window(s).
>
> I don't think it's the same problem, because this one doesn't go away
> when you type something into the minibuffer, as in Dmitry's recipe.
>
> What you see here is normal division of the screen real estate between
> windows in Emacs. This is how it was coded.
OK. Anyway, there are better ways to use that extra space. IMO it
should be given to the main window(s).
BTW, I filed a bug report about this:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7004
--
Dani Moncayo
next prev parent reply other threads:[~2013-01-21 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 6:34 Mini-window glitch with GTK Dmitry Antipov
2013-01-21 7:15 ` Dani Moncayo
2013-01-21 17:19 ` Eli Zaretskii
2013-01-21 17:29 ` Dani Moncayo [this message]
2013-01-21 12:30 ` Xue Fuqiao
2013-01-21 13:08 ` Dmitry Antipov
2013-01-21 17:24 ` Eli Zaretskii
2013-01-22 4:55 ` Dmitry Antipov
2013-01-22 7:57 ` Eli Zaretskii
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='CAH8Pv0hz=XySKVMTo5OzqMRaG1g7cL8WQ5XvbbKFfrYvQ884ig@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.