bug#12354: 24.2; garbage inserted at the beginning of the buffer even when xterm-extra-capabilities is t

[Stefan Monnier <monnier@IRO.UMontreal.CA>]

>> The timeout is present because we prefer having garbage in those
>> (presumably rare) cases where the terminal answers too late, over having
>> Emacs hang forever (tho it's not a hard-hang) when the terminal doesn't
>> understand the request.
> Won't C-g have any effect?

As I said, it's not a hard hang.  Even just hitting any key should get
you out of it (but the key is eaten along the way).

> Perhaps, in case of timeout and some data have been written to the
> buffer before a cursor move, Emacs should warn about this when the
> user saves the buffer (or perhaps earlier). When this happens, there
> are two possibilities:

If you look at the code, you'll hopefully see that there are 2 code
paths (one synchronous with a timeout, and one asynchronous), and
a comment saying that the two should be merged.
I.e. when using the synchronous path, after hitting the timeout, we
should switch to the async path.
Or simply just "always" use the async path.


        Stefan