unofficial mirror of bug-gnu-emacs@gnu.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: Mon, 28 Mar 2016 14:39:31 +0200	[thread overview]
Message-ID: <87io06u67w.fsf@gmx.net> (raw)
In-Reply-To: <56F9140C.9050709@gmx.at> (martin rudalics's message of "Mon, 28 Mar 2016 13:22:52 +0200")

On Mon, 28 Mar 2016 13:22:52 +0200 martin rudalics <rudalics@gmx.at> wrote:

>>>> Let's start with a much simpler reproducer:
>>>>
>>>>     . emacs -Q
>>>>     . Type "C-x" and wait until you see "C-x-" in the echo area
>>>>     . Type "5 2"
>>>>
> [...]
>> I inadvertantly executed Eli's recipe yesterday and noticed an
>> additional oddity, seen in this screenshot (I didn't realize that that
>> recipe triggered it and since I couldn't otherwise reproduce the oddity
>> and had never seen it before, I didn't feel I had enough information to
>> file a bug):
>
> 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.

>> The extra space in the second frame's minibuffer remains for the life of
>> the frame AFAICT, at least I couldn't find any way to eliminate it.
>
> Not even by displaying an empty or one-line message?

`M-: (message "")' has no effect, nor anything else I've tried
(e.g. `C-x 2 C-x 1', `C-x 3 C-x 1').  

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.

Steve Berman





  reply	other threads:[~2016-03-28 12:39 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 [this message]
2016-03-29 15:13           ` martin rudalics
2016-04-06 19:25             ` Stephen Berman
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

  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=87io06u67w.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 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).