unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Weird behavior and crash with X and TTY frame
Date: Sun, 07 Apr 2013 19:18:44 +0400	[thread overview]
Message-ID: <51618E54.7040102@yandex.ru> (raw)
In-Reply-To: <A0C28228-46D0-431B-A84F-77709146BB7E@swipnet.se>

On 04/07/2013 04:06 PM, Jan Djärv wrote:

> This is something Emacs can't handle.  It is because how the lisp and event loop interracts.
>
> When you do (x-popup-dialog t '("Test" ("yes" . 1))), a Lisp return value is expected back to the Lisp code.
> So Emacs does not execute any more Lisp, until the dialog is popped down.
> The popup is shown by a loop that just processes X events (x_menu_wait_for_event).
> When you switch frame and do C-g C-g, the "normal" stuff does not happen, because Lisp is not executed.
>
> This would be solvable if we had an independent Lisp loop per terminal, but it is not so.
> There is only one Lisp loop, shared by all frames/terminals, and if one frame/terminal suspends the loop,
> it is suspended for all frames/terminals.

Yes, but the same trick with two X frames doesn't crash at least; first C-g on
X frame 2 cancels popup raised on frame 1 and resumes normal event processing loop.

Dmitry





  reply	other threads:[~2013-04-07 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 13:03 Weird behavior and crash with X and TTY frame Dmitry Antipov
2013-04-07 12:06 ` Jan Djärv
2013-04-07 15:18   ` Dmitry Antipov [this message]
2013-04-07 15:40     ` Eli Zaretskii
2013-04-07 15:36   ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2013-04-07 15:02 grischka

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=51618E54.7040102@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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).