From: Lennart Borgman <lennart.borgman@gmail.com>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: grischka <grishka@gmx.de>,
emacs-devel@gnu.org, Jason Rumney <jasonr@gnu.org>
Subject: Re: System calls without error checks in w32
Date: Mon, 7 Jun 2010 17:23:03 +0200 [thread overview]
Message-ID: <AANLkTil5J9r4pa4jQaHqfiHOYz4N57ubzCh3uQLLr-8A@mail.gmail.com> (raw)
In-Reply-To: <87k4qa99l4.fsf@uwakimon.sk.tsukuba.ac.jp>
On Mon, Jun 7, 2010 at 4:54 PM, Stephen J. Turnbull <stephen@xemacs.org> wrote:
> grischka writes:
>
> > XEmacs uses the same thread for lisp and gui and doesn't have any
> > such problem.
>
> XEmacs has such a hairy event loop that it is no longer supported by
> X.org. You may not want to go there.
>
> http://bugs.freedesktop.org/show_bug.cgi?id=13471
> https://trac.macports.org/ticket/18491
> http://bugs.freedesktop.org/show_bug.cgi?id=20048
;-)
I guess the idea of having two event loops/thread is not in itself
bad. If the gui thread is never blocked it can be used to convey
status information at least to the user. (You can put these in
temporary windows inside the frame for example.)
But sometimes I wonder wheter all windows really runs in the gui
threads. And why does not C-g break all looping, even those in timers
(like fontification)? And is it the same trouble on other platfoms or
is it just the w32 port that has this?
And moreover I wonder wether all messages really reach their
destinations or if something is blocking them in certain situations.
(Again, why is not C-g handled in the case above?)
And what is blocking Emacs during the time when a new frame is
created? Why is not that done asynchronously?
next prev parent reply other threads:[~2010-06-07 15:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 9:18 System calls without error checks in w32 grischka
2010-06-05 17:15 ` Jason Rumney
2010-06-07 10:37 ` grischka
2010-06-07 14:54 ` Stephen J. Turnbull
2010-06-07 15:23 ` Lennart Borgman [this message]
2010-06-07 17:21 ` grischka
2010-06-07 17:30 ` Lennart Borgman
2010-06-07 18:54 ` grischka
2010-06-08 0:32 ` Lennart Borgman
2010-06-08 0:34 ` Lennart Borgman
2010-06-07 19:56 ` Stefan Monnier
2010-06-07 23:35 ` Lennart Borgman
-- strict thread matches above, loose matches on Subject: below --
2010-05-29 2:38 Lennart Borgman
2010-05-29 17:43 ` Eli Zaretskii
2010-05-29 18:42 ` Lennart Borgman
2010-05-29 19:35 ` Eli Zaretskii
2010-05-29 20:02 ` Lennart Borgman
2010-05-29 21:25 ` Eli Zaretskii
2010-05-29 21:30 ` Lennart Borgman
2010-05-30 3:02 ` Eli Zaretskii
2010-05-30 3:26 ` Lennart Borgman
2010-05-30 17:36 ` Eli Zaretskii
2010-05-30 18:02 ` Lennart Borgman
2010-05-30 19:24 ` Juanma Barranquero
2010-05-30 22:37 ` Lennart Borgman
2010-05-30 23:03 ` Juanma Barranquero
2010-05-30 23:28 ` Lennart Borgman
2010-05-31 0:10 ` Juanma Barranquero
2010-05-31 0:58 ` Lennart Borgman
2010-05-31 2:02 ` Juanma Barranquero
2010-05-31 2:36 ` Lennart Borgman
2010-05-31 3:06 ` Juanma Barranquero
2010-05-31 3:05 ` Eli Zaretskii
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=AANLkTil5J9r4pa4jQaHqfiHOYz4N57ubzCh3uQLLr-8A@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=grishka@gmx.de \
--cc=jasonr@gnu.org \
--cc=stephen@xemacs.org \
/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).