unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: raman <raman@google.com>
To: David Kastrup <dak@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Severe lossage from unread-command-events
Date: Sat, 08 Aug 2015 08:14:23 -0700	[thread overview]
Message-ID: <p91tws9ak34.fsf@google.com> (raw)
In-Reply-To: <87wpx7hwzu.fsf@fencepost.gnu.org> (David Kastrup's message of "Fri, 07 Aug 2015 18:41:25 +0200")

This may or may not be related -- but it's a problem I've been trying to
nail down for a while.

I most recently encountered it with high repro rates when using package
elfeed -- a feed-reader.

Elfeed keeps an index etc that can grow to 50mb plus -- it opens
those -- and updates them as well using idle  timers.

Effect/Issue: 

When those timers fire, and Emacs opens those archive files, it can pop
up the "file is x mb big, really open?" dialog. Now if this occurs while
you're at the keyboard, answering yes works -- and there is no
problem. However if this prompt occurs if you're away from your
keyboard,  or perhaps  working in  another window, then  it becomes
impossible to answer "yes/no" to that prompt from the  "file is too big"
dialog --- For elfeed the author checked in a fix that avoids the prompt
--- but the fact that an async generated prompt cannot be responded to
later is likely symptomatic of a deeper problem in input processing.


-- 



  reply	other threads:[~2015-08-08 15:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 15:46 Severe lossage from unread-command-events David Kastrup
2015-08-06 14:29 ` Eli Zaretskii
2015-08-06 15:01   ` David Kastrup
2015-08-06 15:25     ` Eli Zaretskii
2015-08-06 15:46       ` David Kastrup
2015-08-06 16:21         ` Eli Zaretskii
2015-08-07 16:08       ` Stefan Monnier
2015-08-07 16:41         ` David Kastrup
2015-08-08 15:14           ` raman [this message]
2015-08-07 18:13         ` Eli Zaretskii
2015-08-06 15:33     ` David Kastrup
2015-08-06 16:10       ` Eli Zaretskii
2015-08-06 16:16         ` David Kastrup
2015-08-06 18:47     ` David Kastrup
2015-08-06 20:00       ` David Kastrup
2015-08-10 16:56         ` David Kastrup
2015-08-10 17:35           ` Eli Zaretskii
2015-08-10 17:47             ` David Kastrup
2015-08-10 18:17               ` Eli Zaretskii
2015-08-10 18:34                 ` David Kastrup

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=p91tws9ak34.fsf@google.com \
    --to=raman@google.com \
    --cc=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).