From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: sorourke@cs.ucsd.edu, jan.h.d@swipnet.se,
mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: [patch] enhanced mac drag-n-drop
Date: Sun, 10 Apr 2005 23:35:55 -0400 [thread overview]
Message-ID: <m1mzs6f0s3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1DKoAF-0000pD-IN@fencepost.gnu.org> (Richard Stallman's message of "Sun, 10 Apr 2005 21:56:35 -0400")
> Jan D. explained the problem, and I will just note that compiling
> with -DSYNC_INPUT should lift that restriction (because it causes
> XTread_socket to not be run from the signal handler any more).
> Do you recall what the disadvantages of -DSYNC_INPUT were?
> I think one disadvantage may have been that the Emacs window would
> not refresh while something was busy. But I am not sure if that
> disadvantage is real. Do you know?
Indeed, it makes signal handling synchronous, i.e. more like
cooperative multithreading: if you forget to use QUIT at some spot, it might
lead to an Emacs process completely unresponsive to C-g.
Note that we already have such occurrences current without
using -DSYNC_INPUT, so it wouldn't be a new class of bugs.
But the screen does get refreshed even while Emacs is busy since signals
processing can be done at any place where we do QUIT.
Other disadantages: it makes the QUIT macro bigger and maybe slower.
I haven't looked at the actual impact and neither have I tried to reduce
this impact.
OTOH, it makes several BLOCK_INPUT unnecessary, including all the
malloc_hook hacks.
For what it's worth I've been using Emacs with -DSYNC_INPUT since before
I installed the patch and haven't noticed any negative impact (except for
a few places where a QUIT was missing, but I haven't bumped into any such
thing for a while now).
Stefan
next prev parent reply other threads:[~2005-04-11 3:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 0:53 [patch] enhanced mac drag-n-drop Sean O'Rourke
2005-04-06 11:37 ` Stefan Monnier
2005-04-06 16:17 ` Jan D.
2005-04-06 18:12 ` Sean O'Rourke
2005-04-06 19:22 ` Jan D.
[not found] ` <uwtrfsjhv.fsf@jasonrumney.net>
2005-04-07 4:36 ` Jan D.
2005-04-07 6:59 ` Jason Rumney
2005-04-07 13:33 ` Sean O'Rourke
2005-04-07 15:18 ` Jan D.
2005-04-11 19:39 ` Jan D.
2005-04-09 11:00 ` YAMAMOTO Mitsuharu
2005-04-09 13:46 ` Jan D.
2005-04-10 2:03 ` YAMAMOTO Mitsuharu
2005-04-10 5:47 ` Jan D.
2005-04-10 14:42 ` Stefan Monnier
2005-04-11 1:56 ` Richard Stallman
2005-04-11 3:35 ` Stefan Monnier [this message]
2005-04-11 9:49 ` YAMAMOTO Mitsuharu
2005-04-11 16:39 ` Stefan Monnier
2005-04-12 8:24 ` YAMAMOTO Mitsuharu
2005-04-12 2:58 ` Richard Stallman
2005-04-12 3:59 ` Stefan Monnier
2005-04-12 17:24 ` Richard Stallman
2005-04-11 1:56 ` Richard Stallman
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=m1mzs6f0s3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=mituharu@math.s.chiba-u.ac.jp \
--cc=sorourke@cs.ucsd.edu \
/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).