From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23124@debbugs.gnu.org
Subject: bug#23124: Two minibuffer resize related bugs
Date: Tue, 29 Mar 2016 17:12:56 +0200 [thread overview]
Message-ID: <56FA9B78.5050800@gmx.at> (raw)
In-Reply-To: <831t6vzv9b.fsf@gnu.org>
>> (1) Save the attached foo.el file somewhere and make its first line match
>> the location where you stored it.
>>
>> (2) Start Emacs with the options -Q and -l to load foo.el.
>>
>> (3) Type C-x 5 2.
>>
>> (4) Go back to the initial frame, move to the end of the last non-empty
>> line after ";; (bar)" and type C-x C-e.
>>
>> At this moment "nothing" happens here (Bug#1). When I now switch (via
>> Alt TAB) to the new frame (the one created via C-x 5 2), the message
>> appears there. When I now type C-p in the new frame, the minibuffer
>> window shrinks back but the space previously occupied by the modeline of
>> the window above is not redrawn, hence I get two modelines above each
>> other (Bug#2).
I've now traced this behavior back to this
commit 9d6ec23f7d4f8fbbfdcea353c4b58e47f76a7342
Author: Eli Zaretskii <eliz@gnu.org>
Date: Sat Oct 24 18:54:15 2015 +0300
Update frame title when redisplay scrolls selected window
* src/xdisp.c (redisplay_window): Reconsider the frame's title
when the mode-line of the frame's selected window needs to be
updated.
In fact, removing the
x_consider_frame_title (w->frame);
call from redisplay_window fixes both bugs here.
> 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"
>
> Result: a new frame is displayed, with both frames showing the
> "C-x 5 2" echo, which already sounds like a bug (only one frame should
> show it).
>
> Now type "C-p" -- only one of the two echo messages will disappear,
> the one in the non-selected window stays put.
>
> This didn't happen in Emacs 24.5, where the "C-x 5 2" echo is first
> cleared, and then redisplayed after the new frame is created.
>
> According to my testing, this problem appeared between Aug 31 and Sep
> 30 last year.
This a different problem preceding the one I described.
martin
next prev parent reply other threads:[~2016-03-29 15:12 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
2016-03-29 15:12 ` martin rudalics [this message]
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=56FA9B78.5050800@gmx.at \
--to=rudalics@gmx.at \
--cc=23124@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.