GNU bug report logs - #80017
31.0.50; single minibuffer frame broken for non-NIL values of resize-mini-frames

Previous Next

To reply to this bug, email your comments to 80017 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Madhu <enometh <at> meer.net>
To: bug-gnu-emacs <at> gnu.org
Subject: 31.0.50; single minibuffer frame broken for non-NIL values of
 resize-mini-frames
Date: Tue, 16 Dec 2025 15:53:28 +0530 (IST)

Hello, I used to be able to use a single dedicated minibuffer with
(setq resize-mini-mode 'grow-only), but with 'grow-only or t
this now results in:
Error during redisplay: (window--resize-mini-frame #<frame  *Minibuf-1* 0xdbdad8>) signaled (quit)

To reproduce you can try starting emacs with
emacs -Q -eval "(setq initial-frame-alist '((minibuffer)) default-frame-alist '((minibuffer)) minibuffer-auto-raise t resize-mini-frames nil)"

which should work normally.

However setting (setq resize-mini-frame 'grow-only) and invoking some
minibuffer command say (M-x info), will hang redisplay until ^G quit,
and then print the error message.

[If this is not reproducible, I can provide the code
activate-single-minibuffer mode that I use.]

Message #8 received at 80017 <at> debbugs.gnu.org (full text, mbox):

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: 80017 <at> debbugs.gnu.org
Cc: Madhu <enometh <at> meer.net>
Subject: Re: bug#80017: 31.0.50; single minibuffer frame broken for non-NIL
 values of resize-mini-frames
Date: Tue, 16 Dec 2025 11:38:18 +0000

Hello,

On Tue 16 Dec 2025 at 03:53pm +0530, Madhu wrote:

> Hello, I used to be able to use a single dedicated minibuffer with
> (setq resize-mini-mode 'grow-only), but with 'grow-only or t
> this now results in:
> Error during redisplay: (window--resize-mini-frame #<frame  *Minibuf-1* 0xdbdad8>) signaled (quit)
>
> To reproduce you can try starting emacs with
> emacs -Q -eval "(setq initial-frame-alist '((minibuffer)) default-frame-alist '((minibuffer)) minibuffer-auto-raise t resize-mini-frames nil)"
>
> which should work normally.
>
> However setting (setq resize-mini-frame 'grow-only) and invoking some
> minibuffer command say (M-x info), will hang redisplay until ^G quit,
> and then print the error message.
>
> [If this is not reproducible, I can provide the code
> activate-single-minibuffer mode that I use.]

Can you use 'git bisect' to identify the commit that seems to have
introduced the problem?

-- 
Sean Whitton

Message #11 received at 80017 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Madhu <enometh <at> meer.net>
Cc: 80017 <at> debbugs.gnu.org
Subject: Re: bug#80017: 31.0.50;
 single minibuffer frame broken for non-NIL values of
 resize-mini-frames
Date: Tue, 16 Dec 2025 15:34:13 +0200

> Date: Tue, 16 Dec 2025 15:53:28 +0530 (IST)
> From:  Madhu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> Hello, I used to be able to use a single dedicated minibuffer with
> (setq resize-mini-mode 'grow-only), but with 'grow-only or t

You mean, resize-mini-windows, yes?

> this now results in:
> Error during redisplay: (window--resize-mini-frame #<frame  *Minibuf-1* 0xdbdad8>) signaled (quit)
>
> 
> To reproduce you can try starting emacs with
> emacs -Q -eval "(setq initial-frame-alist '((minibuffer)) default-frame-alist '((minibuffer)) minibuffer-auto-raise t resize-mini-frames nil)"
> 
> which should work normally.

It does work normally, but what do you do after starting Emacs as
above to reproduce the problem?  If I type

  (setq resize-mini-mode 'grow-only) C-x C-e

I don't see any errors in *Messages*.

Message #14 received at 80017 <at> debbugs.gnu.org (full text, mbox):

From: Madhu <enometh <at> meer.net>
To: eliz <at> gnu.org
Cc: 80017 <at> debbugs.gnu.org
Subject: Re: bug#80017: 31.0.50; single minibuffer frame broken for non-NIL
 values of resize-mini-frames
Date: Wed, 17 Dec 2025 07:08:44 +0530 (IST)

*  Eli Zaretskii <eliz <at> gnu.org> <867bum5z56.fsf <at> gnu.org>
Wrote on Tue, 16 Dec 2025 15:34:13 +0200
>> Hello, I used to be able to use a single dedicated minibuffer with
>> (setq resize-mini-mode 'grow-only), but with 'grow-only or t
> You mean, resize-mini-windows, yes?

mea typo culpa.  I meant resize-mini-frames,  (I got it right in the subject line and in the recipe command but failed here)

>> this now results in:
>> Error during redisplay: (window--resize-mini-frame #<frame  *Minibuf-1* 0xdbdad8>) signaled (quit)
>> To reproduce you can try starting emacs with
>> emacs -Q -eval "(setq initial-frame-alist '((minibuffer)) default-frame-alist '((minibuffer)) minibuffer-auto-raise t resize-mini-frames nil)"
>> which should work normally.
> It does work normally, but what do you do after starting Emacs as
> above to reproduce the problem?  If I type
>   (setq resize-mini-mode 'grow-only) C-x C-e
> I don't see any errors in *Messages*.

That should be resize-mini-frames.  I set it either in emacs, or by modifying the commandline recipe to do

 emacs -Q -eval  "(setq initial-frame-alist '((minibuffer)) default-frame-alist '((minibuffer)) minibuffer-auto-raise t resize-mini-frames 'grow-only)"

then typing any minibuffer command like M-x info hangs when I start typing, until I break it with C-g, and then the message appears in *Messages*.

>> However setting (setq resize-mini-frame 'grow-only) and invoking some
>> minibuffer command say (M-x info), will hang redisplay until ^G quit,
>> and then print the error message.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.