unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Derek Upham <sand@blarg.net>
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 17:11:17 +0100	[thread overview]
Message-ID: <87pq0an5ui.fsf@gmx.de> (raw)
In-Reply-To: <87fw16254c.fsf@priss.frightenedpiglet.com> (Derek Upham's message of "Fri, 08 Feb 2013 07:32:35 -0800")

Derek Upham <sand@blarg.net> writes:

> 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.

Would be interesting. Alternatively, you could also stress via file
notifications. Eval

(defun my-inotify-handler (&rest args)
  (message (format "Here I am '%s'" args)))
(inotify-add-watch "/tmp" t 'my-inotify-handler)

And in a shell outside Emacs, you call

# while /bin/true; do touch /tmp/123; done

> Derek

Best regards, Michael.



  reply	other threads:[~2013-02-08 16:11 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
2013-02-08 16:11             ` Michael Albinus [this message]
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

  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=87pq0an5ui.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=sand@blarg.net \
    /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).