unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kim Storm <storm@cua.dk>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chong Yidong <cyd@stupidchicken.com>, Emacs-devel@gnu.org
Subject: Re: The history of sit_for vs sit-for
Date: Fri, 30 May 2014 20:10:12 +0200	[thread overview]
Message-ID: <5388C984.5010307@cua.dk> (raw)
In-Reply-To: <jwvvbsngub1.fsf-monnier+emacs@gnu.org>

On 2014-05-30 17:32, Stefan Monnier wrote:
>> Maybe this thread will explain why and how...
>> http://lists.gnu.org/archive/html/emacs-devel/2006-07/msg00401.html
> 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.

Kim



  reply	other threads:[~2014-05-30 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 14:18 The history of sit_for vs sit-for Stefan Monnier
2014-05-29 20:19 ` Kim Storm
2014-05-30 15:32   ` Stefan Monnier
2014-05-30 18:10     ` Kim Storm [this message]
2014-05-30 18:31       ` Stefan Monnier

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=5388C984.5010307@cua.dk \
    --to=storm@cua.dk \
    --cc=Emacs-devel@gnu.org \
    --cc=cyd@stupidchicken.com \
    --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).