From: Chris Gray <christopher.gray@mail.mcgill.ca>
Subject: Re: antialiasing for emacs
Date: Mon, 28 Jul 2003 13:22:29 -0700 [thread overview]
Message-ID: <87fzkq9zay.fsf@chicolini.ods.org> (raw)
In-Reply-To: <200307282004.h6SK49wP016439@rum.cs.yale.edu> (Stefan Monnier's message of "Mon, 28 Jul 2003 16:04:09 -0400")
On Mon, 28 Jul 2003, Stefan Monnier wrote:
>> Chris Gray <christopher.gray@mail.mcgill.ca> writes:
>> > Yep. It happens when I start gnus too. I really don't know why,
>> > and these "async errors" seem very hard to debug.
>>
>> Hmmm, actually, come to think of it, there's a function to make
>> emacs use X `synchronously', which might make debugging easier...
>>
>> x-synchronize is a built-in function.
>> (x-synchronize ON &optional DISPLAY)
>>
>> If ON is non-nil, report errors as soon as the erring request is
>> made. If ON is nil, allow buffering of requests. This is a
>> noop on Mac OS systems. The optional second argument DISPLAY
>> specifies which display to act on. DISPLAY should be either a
>> frame or a display name (a string). If DISPLAY is omitted or
>> nil, that stands for the selected frame's display.
>>
>> -Miles
>
> I don't think it's going to help. The `async error' is generally
> due to missing BLOCK_INPUT statements that lead to Xlib functions
> being called from the signal handler while we're already inside
> an Xlib function.
This is exactly what the problem was. In my patch you will notice
that I had BLOCK_INPUT and UNBLOCK_INPUT commented for some strange
reason. Uncommenting it made the async errors go away.
I want to fix some other things before sending another patch, but
those who are already testing my first patch should know what to do.
Cheers,
Chris
next prev parent reply other threads:[~2003-07-28 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 20:37 antialiasing for emacs Chris Gray
2003-07-25 2:02 ` Miles Bader
2003-07-25 19:07 ` Chris Gray
2003-07-27 22:33 ` Miles Bader
2003-07-28 20:04 ` Stefan Monnier
2003-07-28 20:22 ` Chris Gray [this message]
2003-08-13 10:48 ` Miles Bader
2003-07-30 20:31 ` Richard Stallman
2003-07-31 14:35 ` Stefan Monnier
2003-07-27 4:28 ` Marcelo Toledo
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=87fzkq9zay.fsf@chicolini.ods.org \
--to=christopher.gray@mail.mcgill.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.