all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Noam Postavsky <npostavs@users.sourceforge.net>,
	Alexander Shukaev <emacs@Alexander.Shukaev.name>
Cc: 29095@debbugs.gnu.org
Subject: bug#29095: Bug: The '20a09de953f437109a098fa8c4d380663d921481' merge increased my Emacs configuration loading time from 9 s to 60 s
Date: Sun, 05 Nov 2017 11:53:24 +0100	[thread overview]
Message-ID: <59FEEDA4.4040602@gmx.at> (raw)
In-Reply-To: <87y3nl7g8l.fsf@users.sourceforge.net>

 > Perhaps the thing to do is simply to disable x-wait-for-event-timeout if
 > we end up hitting the timeout.  Under most window managers the frame
 > becomes visible much faster than 100ms anyway, as far as I know.

If and when we do that, we should also warn and inform the user.  And we
probably should collect information about those window managers that are
not able to inform us in due time that the frame has become visible.

And maybe we're also still missing one or the other case where we could
set the visibility of the frame.  Alexander, can you try using the
debugger to see if Emacs receives any events that OT1H do not call
SET_FRAME_VISIBLE (f, 1) but OTOH still qualify as ones that make sense
only if the frame is visible?  I know it's a vague question but this is
primarily a timing issue and as such rather subtle.

martin





  parent reply	other threads:[~2017-11-05 10:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01  0:44 bug#29095: Bug: The '20a09de953f437109a098fa8c4d380663d921481' merge increased my Emacs configuration loading time from 9 s to 60 s Alexander Shukaev
2017-11-01  1:31 ` Noam Postavsky
2017-11-01 23:49   ` Alexander Shukaev
2017-11-02  0:21     ` Noam Postavsky
2017-11-04 23:28       ` Alexander Shukaev
2017-11-04 23:53         ` Noam Postavsky
2017-11-04 23:58           ` Alexander Shukaev
2017-11-05 10:53           ` martin rudalics [this message]
2017-11-07  9:10             ` Noam Postavsky
2017-11-07 12:57               ` Noam Postavsky
2017-11-08  7:13               ` martin rudalics
2017-11-08 13:42                 ` Noam Postavsky
2017-11-09  7:28                   ` martin rudalics
2017-11-09 13:20                     ` Noam Postavsky
2017-11-09 18:12                       ` martin rudalics
2017-11-09 22:09                         ` Alexander Shukaev
2017-11-09 22:22                           ` Alexander Shukaev
2017-11-10  0:53                           ` Noam Postavsky
2019-04-23  2:52                             ` Noam Postavsky
2017-11-12 10:09                           ` martin rudalics
2017-11-08  7:13               ` martin rudalics
2017-11-01  3:44 ` 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=59FEEDA4.4040602@gmx.at \
    --to=rudalics@gmx.at \
    --cc=29095@debbugs.gnu.org \
    --cc=emacs@Alexander.Shukaev.name \
    --cc=npostavs@users.sourceforge.net \
    /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.