From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 48629@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#48629: 28.0.50; GUI emacsclient frames stop accepting keyboard input around recv
Date: Wed, 26 May 2021 21:59:44 +0300 [thread overview]
Message-ID: <83cztd9v8f.fsf@gnu.org> (raw)
In-Reply-To: <87a6ohpdrd.fsf@tcd.ie> (contovob@tcd.ie)
> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Cc: schwab@linux-m68k.org, 48629@debbugs.gnu.org
> Date: Wed, 26 May 2021 19:10:30 +0100
>
> > IOW, when you find Emacs stuck in pselect, type "finish" and let Emacs
> > exit the pselect call.
>
> I did this, and it returned zero after a while:
So it found no input available.
> > Is the keyboard descriptor in the set of descriptors pselect waits
> > for?
>
> How do I determine what the keyboard descriptor is?
Look at fd_callback_info[desc].flags for values of DESC from zero to
max_desc, and see if any of them have the FOR_READ and KEYBOARD_FD
flags set. Then see whether those descriptors, which have those flags
set, have their bit set in readfds set passed to pselect.
next prev parent reply other threads:[~2021-05-26 18:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 16:14 bug#48629: 28.0.50; GUI emacsclient frames stop accepting keyboard input around recv Basil L. Contovounesios
2021-05-24 16:36 ` Eli Zaretskii
2021-05-24 16:56 ` Basil L. Contovounesios
2021-05-24 16:59 ` Eli Zaretskii
2021-05-24 17:12 ` Basil L. Contovounesios
2021-05-24 17:45 ` Andreas Schwab
2021-05-24 18:38 ` Basil L. Contovounesios
2021-05-24 19:00 ` Andreas Schwab
2021-05-26 15:25 ` Basil L. Contovounesios
2021-05-26 15:58 ` Basil L. Contovounesios
2021-05-26 17:24 ` Eli Zaretskii
2021-05-26 18:10 ` Basil L. Contovounesios
2021-05-26 18:59 ` Eli Zaretskii [this message]
2021-06-03 13:18 ` Basil L. Contovounesios
2021-05-26 17:21 ` Eli Zaretskii
2022-07-15 10:24 ` Lars Ingebrigtsen
2022-07-24 3:54 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-24 9:25 ` Lars Ingebrigtsen
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=83cztd9v8f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48629@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=schwab@linux-m68k.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).