[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Severe lossage from unread-command-events
From: |
raman |
Subject: |
Re: Severe lossage from unread-command-events |
Date: |
Sat, 08 Aug 2015 08:14:23 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
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.
--
- Severe lossage from unread-command-events, David Kastrup, 2015/08/05
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, Eli Zaretskii, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/06
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/10
- Re: Severe lossage from unread-command-events, Eli Zaretskii, 2015/08/10
- Re: Severe lossage from unread-command-events, David Kastrup, 2015/08/10
- Re: Severe lossage from unread-command-events, Eli Zaretskii, 2015/08/10