unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 1291@emacsbugs.donarmstrong.com
Subject: bug#1291: 23.0.60; 1) resize-mini-windows: customizable, 2) if grow mini, grow	Completions
Date: Mon, 03 Nov 2008 09:58:34 +0100	[thread overview]
Message-ID: <490EBD3A.7000607@gmx.at> (raw)
In-Reply-To: <00a001c93d8d$25b016b0$0200a8c0@us.oracle.com>

 > In sum, if *Completions* is visible during minibuffer completion, then the
 > minibuffer should take its window into account. If not, it need not worry about
 > it.

Ever since 1999 this is handled by Gerd's shrink_window_lowest_first
function.  That function takes lines from the window above the
minibuffer window and IIUC currently doesn't even care about fixed-size
windows.  It certainly doesn't care about what _kind of buffer_ is
displayed in that window.  Moreover, the code responsible for re-growing
the window after the minibuffer is re-shrunk will grow the lowest window
again and we'll be left with a spare line if we earlier shrank the upper
window.

So the only solution I can think of is to convey some information to
shrink_window_lowest_first, with the help of a buffer-local variable,
telling that a window showing that buffer should not be resized if it is
possible to resize another window instead.

martin







  reply	other threads:[~2008-11-03  8:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02  0:16 bug#1291: 23.0.60; 1) resize-mini-windows: customizable, 2) if grow mini, grow Completions Drew Adams
2008-11-02 14:12 ` martin rudalics
2008-11-02 14:49   ` Drew Adams
2008-11-02 15:12   ` Drew Adams
2008-11-02 18:14     ` martin rudalics
2008-11-02 19:05       ` Drew Adams
2008-11-02 19:45         ` martin rudalics
2008-11-02 20:27           ` Drew Adams
2008-11-03  7:17             ` martin rudalics
2008-11-03  8:21               ` Drew Adams
2008-11-03  8:58                 ` martin rudalics [this message]
2008-11-05 10:37               ` Kevin Rodgers
2008-11-05 12:52                 ` martin rudalics
2014-12-25 19:29 ` martin rudalics
  -- strict thread matches above, loose matches on Subject: below --
2008-11-03 19:34 Chong Yidong
2008-11-03 20:05 ` Drew Adams
2008-11-04  7:36 ` martin rudalics
2008-11-04 14:28   ` Drew Adams
2008-11-04 16:48     ` martin rudalics
2008-11-04 17:00       ` Drew Adams
2008-11-04 16:56   ` Chong Yidong

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=490EBD3A.7000607@gmx.at \
    --to=rudalics@gmx.at \
    --cc=1291@emacsbugs.donarmstrong.com \
    --cc=drew.adams@oracle.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).