Nicer way to wake sit-for up?

Nicer way to wake sit-for up?

[spamfilteraccount]

I have a code where the command loop executes a command which is
waiting for arriving data with sit-for. When the data arrives from the
network a callback is invoked and I wake sit-for up with a dummy event
like this:

the callback:

  ...
  (setq unread-command-events (cons 'data-arrived
unread-command-events))
  ...


the command:

  ...
  (sit-for 5)
  (if (eq (car unread-command-events) 'data-arrived)
    (setq unread-command-events (cdr unread-command-events)))
  ...


It works, but feels a bit clumsy. Is it a simpler or nicer way to do
this?

Re: Nicer way to wake sit-for up?

[Johan Bockgård]

spamfilteraccount@gmail.com writes:

> I have a code where the command loop executes a command which is
> waiting for arriving data with sit-for. When the data arrives from
> the network a callback is invoked and I wake sit-for up with a dummy
> event like this:

[...]

> It works, but feels a bit clumsy. Is it a simpler or nicer way to do
> this?

`accept-process-output'

-- 
Johan Bockgård

Re: Nicer way to wake sit-for up?

[Kim F. Storm]

spamfilteraccount@gmail.com writes:

> I have a code where the command loop executes a command which is
> waiting for arriving data with sit-for. When the data arrives from the
> network a callback is invoked and I wake sit-for up with a dummy event
> like this:
>
> the callback:
>
>   ...
>   (setq unread-command-events (cons 'data-arrived
> unread-command-events))
>   ...
>

I can't think of a better way here, but you can just write

  (push 'data-arrived unread-command-events)



>
>   ...
>   (sit-for 5)
>   (if (eq (car unread-command-events) 'data-arrived)
>     (setq unread-command-events (cdr unread-command-events)))
>   ...

You could arrange for the data-arrived event to be ignored, e.g.

(define-key global-map [data-arrived] 'ignore)



Perhaps, you could use ignore instead of data-arrived, i.e.

   (define-key global-map [ignore] 'ignore)
 
and

   (push 'ignore unread-command-events)


-- 
Kim F. Storm  http://www.cua.dk

Re: Nicer way to wake sit-for up?

[David Kastrup]

no-spam@cua.dk (Kim F. Storm) writes:

> spamfilteraccount@gmail.com writes:
>
>> I have a code where the command loop executes a command which is
>> waiting for arriving data with sit-for. When the data arrives from the
>> network a callback is invoked and I wake sit-for up with a dummy event
>> like this:
>>
>> the callback:
>>
>>   ...
>>   (setq unread-command-events (cons 'data-arrived
>> unread-command-events))
>>   ...
>>
>
> I can't think of a better way here, but you can just write
>
>   (push 'data-arrived unread-command-events)
>>
>>   ...
>>   (sit-for 5)
>>   (if (eq (car unread-command-events) 'data-arrived)
>>     (setq unread-command-events (cdr unread-command-events)))
>>   ...
>
> You could arrange for the data-arrived event to be ignored, e.g.
>
> (define-key global-map [data-arrived] 'ignore)
>
>
>
> Perhaps, you could use ignore instead of data-arrived, i.e.
>
>    (define-key global-map [ignore] 'ignore)
>  
> and
>
>    (push 'ignore unread-command-events)

Maybe (push 'mouse-movement unread-command-events) would do the trick?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Nicer way to wake sit-for up?

[spamfilteraccount]

Thanks for the ideas.

I'm a little surprised there is no built-in function to do that. It's a
pretty essential operation when having to work with asynchronous
requests.