From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 15046@debbugs.gnu.org
Subject: bug#15046: 24.3.50; Extra Line under minibuffer in Mac OSX fullscreen
Date: Fri, 09 Aug 2013 16:51:55 +0300 [thread overview]
Message-ID: <83haezrmys.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0gP6TJX6LCtzJ09vi8xK=uijn-230Dg_pY_3pdD5xnFFw@mail.gmail.com>
> Date: Fri, 9 Aug 2013 15:30:24 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: 15046@debbugs.gnu.org
>
> IMO, it is much better to give the leftover space to the main
> window(s) than to the mini-window. The main reason I can think of now
> is that the main window(s) is (are) more likely to have more text
> beyond its last wholly-visible line than the mini-window (which
> usually will not need more than one line).
But OTOH the other windows are taller, so they have more lines than
the poor little minibuffer window.
next prev parent reply other threads:[~2013-08-09 13:51 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 19:39 bug#15046: 24.3.50; Extra Line under minibuffer in Mac OSX fullscreen Deyuan Deng
2013-08-08 17:58 ` Jan Djärv
2013-08-09 10:22 ` Eli Zaretskii
2013-08-09 11:03 ` Dani Moncayo
2013-08-09 11:26 ` Dani Moncayo
2013-08-09 12:23 ` martin rudalics
2013-08-09 13:19 ` Dani Moncayo
2013-08-09 17:08 ` martin rudalics
2013-08-09 12:58 ` Jan Djärv
2013-08-09 13:14 ` Dani Moncayo
2013-08-09 12:22 ` martin rudalics
2013-08-09 13:17 ` Eli Zaretskii
2013-08-09 13:30 ` Dani Moncayo
2013-08-09 13:51 ` Eli Zaretskii [this message]
2013-08-09 13:53 ` Dani Moncayo
2013-08-09 13:52 ` Dani Moncayo
2013-08-09 14:13 ` Eli Zaretskii
2013-08-09 14:23 ` Dani Moncayo
2013-08-09 16:19 ` Stefan Monnier
2013-08-09 16:59 ` Dani Moncayo
2013-08-09 18:57 ` Stefan Monnier
2013-08-11 17:14 ` Dani Moncayo
2013-08-09 17:10 ` martin rudalics
2013-12-17 10:38 ` Dani Moncayo
2013-12-18 2:12 ` Deyuan Deng
2013-08-09 12:41 ` Jan Djärv
2013-08-09 13:37 ` Eli Zaretskii
2013-08-09 15:39 ` Deyuan Deng
2013-08-09 17:08 ` martin rudalics
2013-08-09 18:57 ` Deyuan Deng
2013-08-08 19:21 ` Deyuan Deng
2013-08-08 21:06 ` Jan Djärv
2013-08-09 9:12 ` martin rudalics
2013-08-09 9:52 ` Jan Djärv
2013-08-09 12:22 ` 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=83haezrmys.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15046@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
/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).