From: Derek Upham <sand@blarg.net>
To: "Michael Albinus" <michael.albinus@gmx.de>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
Subject: Re: read_char() does not detect, handle special-event-map buffer changes
Date: Fri, 08 Feb 2013 07:32:35 -0800 [thread overview]
Message-ID: <87fw16254c.fsf@priss.frightenedpiglet.com> (raw)
In-Reply-To: <87k3qjcl72.fsf@gmx.de>
Michael Albinus writes:
> Derek Upham <sand@blarg.net> writes:
>
>> This removes a flawed optimization and returns a documented value. It
>> doesn't touch read_key_sequence, so that risk goes away. If we were
>> getting special events at a high rate of speed this /might/ cause a
>> slowdown, but nothing in the special events table seems to be used that
>> way---and I expect that the extra time spent popping back up to
>> read_key_sequence for the retry will still be very fast compared to the
>> time spent in the Emacs Lisp callback.
>
> I don't know what you mean with "high rate of speed", but special events
> are used for D-Bus and for file notifications. There could be a burst of
> incoming events, temporarily.
A couple of emails back I put in a D-Bus handler for asynchronous
messages. I'll set it up to do nothing but push a timestamp onto a
list. Then with a couple of dbus-send instances I can look for rate
differences between the two code paths. I should have numbers this
weekend.
Derek
--
Derek Upham
sand@blarg.net
next prev parent reply other threads:[~2013-02-08 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 8:36 read_char() does not detect, handle special-event-map buffer changes Derek Upham
2013-02-07 6:33 ` Derek Upham
2013-02-07 14:50 ` Derek Upham
2013-02-07 16:25 ` Stefan Monnier
2013-02-08 4:39 ` Derek Upham
2013-02-08 7:35 ` Michael Albinus
2013-02-08 15:32 ` Derek Upham [this message]
2013-02-08 16:11 ` Michael Albinus
2013-02-09 5:31 ` Derek Upham
2013-02-11 19:22 ` Stefan Monnier
2013-02-12 5:29 ` Derek Upham
2013-02-12 14:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fw16254c.fsf@priss.frightenedpiglet.com \
--to=sand@blarg.net \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.