all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: lekktu@gmail.com, eggert@cs.ucla.edu, rms@gnu.org, 12450@debbugs.gnu.org
Subject: bug#12450: Remove configure's --without-sync-input option.
Date: Mon, 17 Sep 2012 10:41:25 +0300	[thread overview]
Message-ID: <83k3vtqeoq.fsf@gnu.org> (raw)
In-Reply-To: <5055B054.5090302@dancol.org>

> Date: Sun, 16 Sep 2012 03:56:20 -0700
> From: Daniel Colascione <dancol@dancol.org>
> CC: eggert@cs.ucla.edu, lekktu@gmail.com, rms@gnu.org, 
>  12450@debbugs.gnu.org
> 
> >> There might be a few lurking bugs, however: one thing that stands
> >> out is that w32term.c, unlike xterm.c, sets interrupt_input_pending,
> >> but doesn't set pending_signals.
> > 
> > Please tell the details about this.
> > 
> 
> I'm still not sure what practical effect this omission would have ---
> on quit, we set Vquit_flag to Qt from the input thread. When Lisp code
> is running, QUIT picks up the non-nilness of Vquit_flag and quits. The
> ELSE_PENDING_SIGNALS branch doesn't apply, so we're able to
> successfully quit.

I added setting pending_signals, it doesn't seem to do any harm, and
playing by the rules has its merit.

> While testing, I ran into a different bug. I'm able to reproduce it on
> the regular w32 build too. Can someone try reproing it with 1) M-:
> (while t) RET, 2) click the menu bar [menu won't appear], 3) C-g, 4)
> typing something? Emacs doesn't seem to respond to typed input.
> Clicking in the Emacs window unblocks everything.

Yes, I see this also.  There's a long comment about this in w32fns.c
around line 2550.  I'm not sure if there's a way to unlock responses
to keyboard input in this scenario; ideas welcome.





      reply	other threads:[~2012-09-17  7:41 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-15  7:54 bug#12450: Remove configure's --without-sync-input option Paul Eggert
2012-09-15  9:32 ` Eli Zaretskii
2012-09-15 10:14   ` Paul Eggert
2012-09-15 11:03     ` Eli Zaretskii
2012-09-15 19:59       ` Paul Eggert
2012-09-15 20:15         ` Eli Zaretskii
2012-09-15 20:31           ` Paul Eggert
2012-09-16  6:33         ` Eli Zaretskii
2012-09-16  7:47           ` Paul Eggert
2012-09-16  8:05             ` Eli Zaretskii
2012-09-16  8:17               ` Paul Eggert
2012-09-16  8:21                 ` Eli Zaretskii
2012-09-16  8:24                 ` Eli Zaretskii
2012-09-16  8:34                   ` Paul Eggert
2012-09-16  8:53                     ` Eli Zaretskii
2012-09-15 21:12     ` Stefan Monnier
2012-09-16  5:55       ` Eli Zaretskii
2012-09-16 14:58         ` Stefan Monnier
2012-09-16 15:45           ` Eli Zaretskii
2012-09-16 16:30             ` Paul Eggert
2012-09-16 18:40               ` Eli Zaretskii
2012-09-16 19:55                 ` Jan Djärv
2012-09-16 18:37             ` Stefan Monnier
2012-09-16  9:33   ` Daniel Colascione
2012-09-16 10:43     ` Eli Zaretskii
2012-09-16 15:10       ` Stefan Monnier
2012-09-16 15:40         ` Eli Zaretskii
2012-09-15 22:18 ` Richard Stallman
2012-09-16  3:15   ` Paul Eggert
2012-09-16  6:10     ` Eli Zaretskii
2012-09-16  8:23       ` Paul Eggert
2012-09-16  8:32         ` Eli Zaretskii
2012-09-16 21:48           ` Paul Eggert
2012-09-17  7:42             ` Eli Zaretskii
2012-09-21 20:50               ` Paul Eggert
2012-09-22  9:03                 ` Eli Zaretskii
2012-09-22  9:34                   ` Paul Eggert
2012-09-22  9:50                     ` Eli Zaretskii
2012-09-22 10:01                       ` Paul Eggert
2012-09-16  9:52         ` Daniel Colascione
2012-09-16 10:44           ` Eli Zaretskii
2012-09-16 10:56             ` Daniel Colascione
2012-09-17  7:41               ` Eli Zaretskii [this message]

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=83k3vtqeoq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12450@debbugs.gnu.org \
    --cc=dancol@dancol.org \
    --cc=eggert@cs.ucla.edu \
    --cc=lekktu@gmail.com \
    --cc=rms@gnu.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 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.