[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Aborting display. Is this possible?
From: |
Eli Zaretskii |
Subject: |
Re: Aborting display. Is this possible? |
Date: |
Sun, 19 Oct 2014 17:54:25 +0300 |
> From: David Kastrup <address@hidden>
> Date: Sun, 19 Oct 2014 16:32:38 +0200
>
> One possible way to deal with this is not to read characters while
> redisplay is being processed
We already do that, since both keyboard input and redisplay happen in
the same thread.
The problem is that auto-repeat leaves just enough time between the
repeated keystrokes for redisplay to kick in. If auto-repeat would
send many keys in one large block, we would process them all before
attempting to redisplay.
- Aborting display. Is this possible?, Alan Mackenzie, 2014/10/19
- Re: Aborting display. Is this possible?, David Kastrup, 2014/10/19
- Re: Aborting display. Is this possible?,
Eli Zaretskii <=
- Re: Aborting display. Is this possible?, Eli Zaretskii, 2014/10/19
- Re: Aborting display. Is this possible?, Alan Mackenzie, 2014/10/19
- Re: Aborting display. Is this possible?, Eli Zaretskii, 2014/10/19
- Re: Aborting display. Is this possible?, Alan Mackenzie, 2014/10/20
- Re: Aborting display. Is this possible?, David Kastrup, 2014/10/20
- Re: Aborting display. Is this possible?, Alan Mackenzie, 2014/10/20
- Re: Aborting display. Is this possible?, Eli Zaretskii, 2014/10/20
- Re: Aborting display. Is this possible?, Eli Zaretskii, 2014/10/20
- Re: Aborting display. Is this possible?, Stefan Monnier, 2014/10/20
- Re: Aborting display. Is this possible?, Eli Zaretskii, 2014/10/20