unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: resize_mini_window question
Date: Fri, 18 Sep 2020 18:50:57 +0200	[thread overview]
Message-ID: <20200918165057.ccn5i6cothosjd2u@Ergus> (raw)
In-Reply-To: <jwv5z8bhy7e.fsf-monnier+emacs@gnu.org>

On Fri, Sep 18, 2020 at 12:02:13PM -0400, Stefan Monnier wrote:
>> Yes I know.  The problem with this was that in my case the user could be
>> expecting to see as many lines as specified in max-mini-window-height as
>> an integer.
>
>I think that is simply a problem of wrong expectations, which we could
>somewhat fix by tweaking the documentation like you suggested.
>
Maybe:

   DEFVAR_LISP ("max-mini-window-height", Vmax_mini_window_height,
     doc: /* Maximum height for resizing mini-windows (the minibuffer and the echo area).
If a float, it specifies a fraction of the mini-window frame's height.
If an integer, it specifies a number of lines with the frame's default char
height.  */);
   Vmax_mini_window_height = make_float (0.25);

>> The external package used to force an enlarge-window but I feel that
>> this is somehow a workaround.
>
>Indeed.  I think it's important to find a solution to the
>"disappearing prompt" that doesn't involve this since enlarging the
>window is not always an option either.
>
>
I already solved it in icomplete then. If we assume that the problem is
the wrong expectations then the solution is trivial with the current
changes in icomplete.

Best,
Ergus



  reply	other threads:[~2020-09-18 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200918150113.4vz5vq3krfslrwdz.ref@Ergus>
2020-09-18 15:01 ` resize_mini_window question Ergus
2020-09-18 15:30   ` Stefan Monnier
2020-09-18 15:56     ` Ergus
2020-09-18 16:02       ` Stefan Monnier
2020-09-18 16:50         ` Ergus [this message]
2020-09-18 19:49           ` Stefan Monnier
2020-09-18 19:39   ` 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

  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=20200918165057.ccn5i6cothosjd2u@Ergus \
    --to=spacibba@aol.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).