unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pip Cet <pipcet@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 21333@debbugs.gnu.org
Subject: bug#21333: 25.0.50; window-size-change-functions not called after mini-window resize
Date: Fri, 28 Aug 2015 08:19:29 +0000	[thread overview]
Message-ID: <CAOqdjBdZAnzvFbzNJmGmadHutiK9JbMKu=a3umU7Mr57BO197g@mail.gmail.com> (raw)
In-Reply-To: <55E015E3.2050409@gmx.at>

[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]

On Fri, Aug 28, 2015 at 8:03 AM, martin rudalics <rudalics@gmx.at> wrote:

> >> FWIW here resizing a window "manually" makes the mini-window "go normal"
> >> first.
> >
> > Strange, that doesn't work here. Are you using the echo area or the
> > minibuffer to test? I'm using the minibuffer.
>
> It goes back to normal in the echo area but leaves the minibuffer window
> alone as you say.


I had assumed "go normal" meant "shrink back to normal size", which is true
for the echo area but not the minibuffer.


> >>    Resizing the frame leaves the mini-window alone.
> >>
> > ...which means they'll be in an inconsistent state afterwards, having
> been
> > resized while the mini-window was enlarged.
>
> Can you tell me more about this inconsistency?
>

Well, first, to clarify, I was talking about unpatched Emacs, and using
window-size-change-functions in an attempt to catch window size changes.

1. window at 80x24, mini-window at 1 line, window thinks it's 80x24.
Everything okay.
2. mini-window grows to 2 lines
3. window at 80x23, mini-window at 2 lines, window thinks it's 80x24.
Inconsistent, but temporary.
4. user resizes window to 79x23. size-change-functions called.
5. window at 79x23, mini-window at 2 lines, window thinks it's 79x23.
Everything okay again.
6. mini-window shrinks.
7. window at 79x24, mini-window at 1 line, window thinks it's 79x23.
Permanent inconsistency.

Am I missing something here?

Pip

[-- Attachment #2: Type: text/html, Size: 2298 bytes --]

  reply	other threads:[~2015-08-28  8:19 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 22:06 bug#21333: 25.0.50; window-size-change-functions not called after mini-window resize Pip Cet
2015-08-24  8:18 ` martin rudalics
2015-08-24 11:08   ` Pip Cet
2015-08-24 12:41     ` martin rudalics
2015-08-24 14:35 ` Eli Zaretskii
2015-08-24 18:06   ` martin rudalics
2015-08-24 18:30     ` Eli Zaretskii
2015-08-25  7:25       ` martin rudalics
2015-08-25 10:34         ` Pip Cet
2015-08-25 15:19           ` Eli Zaretskii
2015-08-26  7:08           ` martin rudalics
2015-08-25 15:11         ` Eli Zaretskii
2015-08-26  7:09           ` martin rudalics
2015-08-26 15:29             ` Eli Zaretskii
2015-08-27  7:57               ` martin rudalics
2015-08-27 15:29                 ` Eli Zaretskii
2015-08-27 17:05                   ` Pip Cet
2015-08-27 17:59                     ` martin rudalics
2015-08-27 18:04                       ` Pip Cet
2015-08-28  8:03                         ` martin rudalics
2015-08-28  8:19                           ` Pip Cet [this message]
2015-08-28  8:45                             ` Pip Cet
2015-08-27 18:35                     ` Eli Zaretskii
2015-08-27 17:58                   ` martin rudalics
2015-08-24 18:13   ` Pip Cet
2015-08-24 19:03     ` Eli Zaretskii
2015-08-25  7:25       ` martin rudalics
2015-08-25 15:12         ` Eli Zaretskii
2015-08-26  7:09           ` martin rudalics
2015-08-26 10:07             ` Pip Cet
2015-08-26 13:01               ` martin rudalics
2015-08-26 16:00                 ` Pip Cet
2015-08-27  7:59                   ` martin rudalics
2015-08-27 15:25                     ` Eli Zaretskii
2015-08-27 16:35                       ` Pip Cet
2015-08-27 17:59                         ` martin rudalics
2015-08-27 18:57                         ` Eli Zaretskii
2015-08-27 20:49                           ` Pip Cet
2015-08-28 10:02                             ` Eli Zaretskii
2015-08-28 12:34                               ` Pip Cet
2015-08-28 13:13                                 ` Eli Zaretskii
2015-08-28 13:26                                   ` Pip Cet
2015-08-26 15:36               ` Eli Zaretskii
2015-08-27  7:58                 ` martin rudalics
2015-08-27 15:24                   ` Eli Zaretskii
2015-08-27 17:58                     ` martin rudalics
2015-08-27 18:39                       ` Eli Zaretskii
2015-08-27 19:00                         ` Eli Zaretskii
2015-08-28  8:04                           ` martin rudalics
2015-08-28  8:47                             ` Eli Zaretskii
2015-08-28 10:51                               ` martin rudalics
2015-08-28 12:46                                 ` Eli Zaretskii
2015-08-28 13:05                                   ` martin rudalics
2015-08-26 15:32             ` Eli Zaretskii
2015-08-27  7:57               ` martin rudalics

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='CAOqdjBdZAnzvFbzNJmGmadHutiK9JbMKu=a3umU7Mr57BO197g@mail.gmail.com' \
    --to=pipcet@gmail.com \
    --cc=21333@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).