all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matthew Leach <matthew@mattleach.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 18451@debbugs.gnu.org
Subject: bug#18451: 24.4.50; 'toggle-frame-fullscreen' can cut off minibuffer
Date: Thu, 18 Sep 2014 13:01:42 +0100	[thread overview]
Message-ID: <877g11i1cp.fsf@matt-desktop.home> (raw)
In-Reply-To: <541AA6C0.4070604@gmx.at> (martin rudalics's message of "Thu, 18 Sep 2014 11:32:48 +0200")

Hi Martin,

martin rudalics <rudalics@gmx.at> writes:

>>> Does (setq frame-resize-pixelwise t) change anything?
>>
>> I'm afraid not. I'm still seeing the bug after evaluating this form.
>
> Just for the record, even if you eval the form when startin Emacs?

Actually, I hadn't done that, I just evaluated it in the scratch buffer.
However, when I paste this as the first form in my .emacs it seems to
fix the issue! I've been toggling for about 10 minutes now and haven't
seen an occurrence of the bug.

>
>
>> Hm, sorry I think there was a problem in my original trace, I've given
>> it another shot.
>>
>> Here is a bug-free trace:
>>
>> Received ConfigureNotify event for frame: 0x6781b0
>> Received ConfigureNotify event for frame: 0x6781b0
>> Received ConfigureNotify event for frame: (nil)
>> xg_frame_resized(0x6781b0, 1366, 768);
>> configure_frame_size(0x6781b0, 1350, 768, 330584, 1, 0, 1);
>> configure_frame_size(0x6781b0, 1350, 768, 330584, 0, 0, 1);
>> Received ConfigureNotify event for frame: 0x6781b0
>>
>>
>> And a buggy-trace:
>>
>> Received ConfigureNotify event for frame: 0x6781b0
>> Received ConfigureNotify event for frame: (nil)
>> xg_frame_resized(0x6781b0, 1366, 768);
>> configure_frame_size(0x6781b0, 1350, 768, 330584, 1, 0, 1);
>> configure_frame_size(0x6781b0, 1350, 768, 330584, 0, 0, 1);
>> Received ConfigureNotify event for frame: 0x6781b0
>> Received ConfigureNotify event for frame: 0x6781b0
>
> Sorry, I somehow lost the initial part of this thread.  These two traces
> don't document any affect on the minibuffer - the heights (768) are
> always the same.  What does `configure_frame_size' stand for?  

Oops, configure_frame_size should be `change_frame_size' defined in
dispnew.c

> Are the traces here in chronological order or reversed?  

They are in chronological order.

> And how do you get a ConfigureNotify event for a frame `nil'?

I'm not sure, but it seems to be expected behaviour as there is an
explicit test for it in the ConfigureNotify event handler.  The frame is
set to `any' if x_top_window_to_frame returns null.
-- 
Matt





  reply	other threads:[~2014-09-18 12:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 16:20 bug#18451: 24.4.50; 'toggle-frame-fullscreen' can cut off minibuffer dev
2014-09-11 17:33 ` Jan Djärv
2014-09-11 17:52   ` Matthew Leach
2014-09-13  9:55     ` Jan Djärv
2014-09-13 22:13       ` Matthew Leach
2014-09-14  9:20         ` Jan Djärv
2014-09-14 13:32           ` Matthew Leach
2014-09-16 18:38             ` Jan Djärv
2014-09-16 19:16               ` Matthew Leach
2014-09-17 10:02                 ` martin rudalics
2014-09-17 10:38                   ` Matthew Leach
2014-09-18  9:32                     ` martin rudalics
2014-09-18 12:01                       ` Matthew Leach [this message]
2014-09-18 12:41                         ` martin rudalics
2014-09-18 19:45                           ` Jan Djärv
2014-09-19 10:22                             ` Matthew Leach
2014-09-19 11:24                               ` martin rudalics
2014-09-20  7:18                               ` Jan Djärv
2015-01-04 18:09                         ` martin rudalics
2015-02-13 18:24                           ` martin rudalics
2014-09-17 16:05                 ` Jan Djärv

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=877g11i1cp.fsf@matt-desktop.home \
    --to=matthew@mattleach.net \
    --cc=18451@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.