all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 23124@debbugs.gnu.org
Subject: bug#23124: Two minibuffer resize related bugs
Date: Wed, 06 Apr 2016 21:25:44 +0200	[thread overview]
Message-ID: <87wpoabkuf.fsf@gmx.net> (raw)
In-Reply-To: <56FA9B84.40708@gmx.at> (martin rudalics's message of "Tue, 29 Mar 2016 17:13:08 +0200")

On Tue, 29 Mar 2016 17:13:08 +0200 martin rudalics <rudalics@gmx.at> wrote:

>>> I have no idea why C-x 5 2 should resize the echo area in the first
>>> place.  Are you sure this happened with Eli's scenario above?
>>
>> Yes; I verified it before sending my post yesterday, and again just now.
>
> I cannot reproduce the problem here.  Can you get a backtrace from where
> grow_mini_window is called?
>
>> It does, however, appear to be the case that only the first `C-x 5 2'
>> has this effect: typing that key sequence from either the second frame
>> (with the wide echo area/minibuffer) or from the first frame (with the
>> normal echo area/minibuffer) creates a frame with a normal echo area/
>> minibuffer.
>
> Can you try bisecting when this started to appear?

On Wed, 30 Mar 2016 10:38:59 +0200 martin rudalics <rudalics@gmx.at> wrote:

>> Is there something else to do wrt this bug report?
>
> I don't think so.  If Steve's bug is not fixed now, a separate report
> seems due anyway.  

Sorry for the long delay in replying; I was away for a week and only saw
your followup mail and Eli's proposed fix last night and could not
attend to it till now.  I was hopeful that it also fixes the resizing I
observed, but I just built from the latest emacs-25 sources, which
include that fix, tried the recipe and the resizing happened again.
However, I now find that I cannot reliably reproduce it: on repeating
the recipe several times the resizing happened one or two more times but
then no more.  I also tried all previous builds I have, going back to
emacs-25.0.90, and in most cases did not get the resizing, but it did
happen a few times, but again not reproducibly (including the build I
was using when I initially posted my observation to this thread).  So I
guess it's no use trying to bisect or debug the problem, or filing a
separate bug report for it.  Too bad.

>                    And if your "C-x 5 2" scenario is not already covered
> anywhere else, you probably should file a separate report as well.

With Eli's fix I still observe "C-x 5 2" in the new frame's echo area,
irrespective of whether the resizing happens or not.

Steve Berman





  reply	other threads:[~2016-04-06 19:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27 15:34 bug#23124: Two minibuffer resize related bugs martin rudalics
2016-03-27 17:27 ` Eli Zaretskii
2016-03-27 20:51   ` martin rudalics
2016-03-27 21:09     ` Stephen Berman
2016-03-28 11:22       ` martin rudalics
2016-03-28 12:39         ` Stephen Berman
2016-03-29 15:13           ` martin rudalics
2016-04-06 19:25             ` Stephen Berman [this message]
2016-03-29 15:12   ` martin rudalics
2016-03-29 15:25     ` Eli Zaretskii
2016-03-29 16:02       ` martin rudalics
2016-03-29 16:44         ` Eli Zaretskii
2016-03-29 17:20           ` martin rudalics
2016-03-29 17:41             ` Eli Zaretskii
2016-03-30  8:38               ` martin rudalics
2016-03-30 15:25                 ` 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=87wpoabkuf.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=23124@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    /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.