[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The history of sit_for vs sit-for

From: Kim Storm
Subject: Re: The history of sit_for vs sit-for
Date: Fri, 30 May 2014 20:10:12 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

On 2014-05-30 17:32, Stefan Monnier wrote:
Maybe this thread will explain why and how...
Ah, thanks.  Hmm... so it seems it has to do with "internal events" used
for things like help-echo tooltips.  Obviously, in itself that doesn't
justify moving to Elisp, but it's just how it happened.  I think the
justification has to do with the fact that the new sit-for used ELisp
timers, which are much easier to access from ELisp.  Of course, this
proved to suffer from other problems, so we then switched to an
implementation based on read-event which could have been written in
C just as well.

Hmm... thanks ...hmm...

I think it was related to making only (certain) lisp event interrupt sit-for.
It seems moving sit-for to lisp was the easiest way to accomplish that.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]